public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/16442] sims not target-async
Date: Tue, 29 Nov 2022 16:22:14 +0000 [thread overview]
Message-ID: <bug-16442-4717-6maOhs6cID@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16442-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16442
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
See also bug #7505.
I lean toward the RSP approach nowadays; we could remove remote-sim
entirely. The only really tricky thing here, I think, is handling
the sim-specific gdbarch register remapping:
Method(
comment="""
MAP a GDB RAW register number onto a simulator register number. See
also include/...-sim.h.
""",
type="int",
name="register_sim_regno",
params=[("int", "reg_nr")],
predefault="legacy_register_sim_regno",
invalid=False,
)
This is used in a few arches, search for set_gdbarch_register_sim_regno.
Probably the best approach is to just change the sims to use XML
register sets like everything else.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-11-29 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 15:23 [Bug sim/16442] New: " tromey at redhat dot com
2014-03-14 0:46 ` [Bug sim/16442] " vapier at gentoo dot org
2015-03-29 22:16 ` vapier at gentoo dot org
2022-11-29 16:22 ` tromey at sourceware dot org [this message]
2022-12-10 12:25 ` vapier at gentoo dot org
2023-06-13 17:21 ` mark at klomp dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-16442-4717-6maOhs6cID@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).