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/29869] sim: align sim register numbers with gdb register numbers
Date: Fri, 29 Dec 2023 01:35:33 +0000	[thread overview]
Message-ID: <bug-29869-4717-JrWRMVeWyW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29869-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29869

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
The issue for gdbserver integration is that a general request
may arrive, which just means "send all the registers".
So, the server has to know how to iterate over them.
Digging a bit I see this info in some ports, but it's not generically
available via the sim public API.  It works in gdb due to the
synchronicity you point out: gdb and the sim generally agree (or
there is a mapping).

I don't really understand why this info isn't in the cgen model
either, but it doesn't seem to be.

Anyway I suspect a new field in _sim_cpu may be the way to go...

Though looking at this, we also don't know the size of registers.
gdb does, but it doesn't inform the remote of this -- the remote
is expected to know.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-12-29  1:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 12:23 [Bug sim/29869] New: " vapier at gentoo dot org
2023-12-23 19:47 ` [Bug sim/29869] " tromey at sourceware dot org
2023-12-24  0:45 ` vapier at gentoo dot org
2023-12-24 20:11 ` tromey at sourceware dot org
2023-12-25  1:52 ` vapier at gentoo dot org
2023-12-29  1:35 ` tromey at sourceware dot org [this message]
2023-12-29  4:46 ` vapier at gentoo dot org
2023-12-31 22:44 ` tromey at sourceware 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-29869-4717-JrWRMVeWyW@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).