public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mark Goncharov <mark.goncharov@syntacore.com>
To: gdb-patches@sourceware.org
Cc: mga-sc <mark.goncharov@syntacore.com>
Subject: [PATCH] [gdb/riscv] Fix test for riscv: zero register.
Date: Mon,  8 Aug 2022 16:01:47 +0300	[thread overview]
Message-ID: <20220808130147.2715849-1-mark.goncharov@syntacore.com> (raw)

From: mga-sc <mark.goncharov@syntacore.com>

x0 register in riscv must have permanent value.
We already have test for that: gdb/testsuite/riscv-reg-aliases.exp.
This patch fixes 4 test drops.
---
 gdb/riscv-tdep.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/gdb/riscv-tdep.c b/gdb/riscv-tdep.c
index 2d41be96b20..20b613075d5 100644
--- a/gdb/riscv-tdep.c
+++ b/gdb/riscv-tdep.c
@@ -933,6 +933,12 @@ riscv_register_name (struct gdbarch *gdbarch, int regnum)
   return name;
 }
 
+static int
+riscv_cannot_store_register (struct gdbarch *gdbarch, int regnum)
+{
+  return regnum == RISCV_ZERO_REGNUM;
+}
+
 /* Construct a type for 64-bit FP registers.  */
 
 static struct type *
@@ -3822,6 +3828,9 @@ riscv_gdbarch_init (struct gdbarch_info info,
      registers, no matter what the target description called them.  */
   set_gdbarch_register_name (gdbarch, riscv_register_name);
 
+  /* Zero register must have permanent value. */
+  set_gdbarch_cannot_store_register (gdbarch, riscv_cannot_store_register);
+
   /* Override the register group callback setup by the target description
      mechanism.  This allows us to force registers into the groups we
      want, ignoring what the target tells us.  */
-- 
2.37.1


             reply	other threads:[~2022-08-08 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 13:01 Mark Goncharov [this message]
2022-08-09 11:05 ` Andrew Burgess
     [not found]   ` <1274621660047438@mail.yandex.com>
2022-08-10 15:14     ` Andrew Burgess

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=20220808130147.2715849-1-mark.goncharov@syntacore.com \
    --to=mark.goncharov@syntacore.com \
    --cc=gdb-patches@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).