From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 2/5] gdb: or1k: fixup linux regcache comment
Date: Mon, 13 Sep 2021 21:47:57 +0900 [thread overview]
Message-ID: <20210913124800.471680-3-shorne@gmail.com> (raw)
In-Reply-To: <20210913124800.471680-1-shorne@gmail.com>
The old comment was not properly updated from the RISC-V example used.
Update it to match OpenRISC.
---
gdb/or1k-linux-tdep.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/gdb/or1k-linux-tdep.c b/gdb/or1k-linux-tdep.c
index 2ad55f0d9ec..2efb4d0b0f9 100644
--- a/gdb/or1k-linux-tdep.c
+++ b/gdb/or1k-linux-tdep.c
@@ -27,9 +27,10 @@
#include "trad-frame.h"
#include "gdbarch.h"
-/* Define the general register mapping. The kernel puts the PC at offset 0,
- gdb puts it at offset 32. Register x0 is always 0 and can be ignored.
- Registers x1 to x31 are in the same place. */
+/* Define the general register mapping. The kernel and GDB put registers
+ r1 to r31 in the same place. The NPC register is stored at index 32 in
+ linux and 33 in GDB, in GDB 32 is for PPC which is not popupated from linux.
+ Register r0 is always 0 and can be ignored. */
static const struct regcache_map_entry or1k_linux_gregmap[] =
{
--
2.31.1
next prev parent reply other threads:[~2021-09-13 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:47 [OpenRISC] [PATCH 0/5] OpenRISC Linux Native and GDBServer Support Stafford Horne
2021-09-13 12:47 ` [OpenRISC] [PATCH 1/5] gdb: or1k: implement gdb server Stafford Horne
2021-10-20 17:33 ` Tom Tromey
2021-10-20 21:17 ` Stafford Horne
2021-09-13 12:47 ` Stafford Horne [this message]
2021-09-13 12:47 ` [OpenRISC] [PATCH 3/5] gdb: or1k: add generated linux descriptor file Stafford Horne
2021-09-13 12:47 ` [OpenRISC] [PATCH 4/5] gdb: or1k: add native linux support Stafford Horne
2021-09-13 12:48 ` [OpenRISC] [PATCH 5/5] gdb: or1k: add single step for linux native debugging Stafford Horne
2021-10-20 18:20 ` [OpenRISC] [PATCH 0/5] OpenRISC Linux Native and GDBServer Support Tom Tromey
2021-10-20 21:15 ` Stafford Horne
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=20210913124800.471680-3-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.