public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Bernd Edlinger <edlinger@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim: riscv: Fix build issue due to recent binutils commit
Date: Thu,  9 May 2024 15:02:47 +0000 (GMT)	[thread overview]
Message-ID: <20240509150247.2B36E3858D39@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b75187cd9480a35f402bb6c384299bf89091bd7b

commit b75187cd9480a35f402bb6c384299bf89091bd7b
Author: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date:   Thu May 9 07:58:08 2024 +0200

    sim: riscv: Fix build issue due to recent binutils commit
    
    The commit c144f6383379 removed INSN_CLASS_A and
    added INSN_CLASS_ZAAMO and INSN_CLASS_ZALRSC instead,
    which broke the build of the sim for riscv targets.
    
    Fix that by using the new INSN_CLASS types.
    
    Fixes: c144f6383379 ("RISC-V: Support B, Zaamo and Zalrsc extensions.")
    
    Approved-By: Tom Tromey <tom@tromey.com>

Diff:
---
 sim/riscv/sim-main.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/sim/riscv/sim-main.c b/sim/riscv/sim-main.c
index 41973d9dd06..378e6f1dc69 100644
--- a/sim/riscv/sim-main.c
+++ b/sim/riscv/sim-main.c
@@ -1299,7 +1299,8 @@ execute_one (SIM_CPU *cpu, unsigned_word iw, const struct riscv_opcode *op)
 
   switch (op->insn_class)
     {
-    case INSN_CLASS_A:
+    case INSN_CLASS_ZAAMO:
+    case INSN_CLASS_ZALRSC:
       return execute_a (cpu, iw, op);
     case INSN_CLASS_C:
       /* Check whether model with C extension is selected.  */

                 reply	other threads:[~2024-05-09 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240509150247.2B36E3858D39@sourceware.org \
    --to=edlinger@sourceware.org \
    --cc=gdb-cvs@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).