From: Tom Tromey <tom@tromey.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH] RISC-V: Support B, Zaamo and Zalrsc extensions.
Date: Wed, 08 May 2024 08:34:23 -0600 [thread overview]
Message-ID: <87o79g8j9s.fsf@tromey.com> (raw)
In-Reply-To: <CAPpQWtCBHtAYq_ReX=Nvhd1Jm2xdYR4bB5Hko7KrGKPhJg_f7Q@mail.gmail.com> (Nelson Chu's message of "Wed, 8 May 2024 12:37:06 +0800")
>>>>> Nelson Chu <nelson@rivosinc.com> writes:
> Committed since these are ratified.
Hi. This seems to have broken the sim build:
../../binutils-gdb/sim/riscv/sim-main.c: In function ‘execute_one’:
../../binutils-gdb/sim/riscv/sim-main.c:1302:10: error: ‘INSN_CLASS_A’ undeclared (first use in this function); did you mean ‘INSN_CLASS_H’?
1302 | case INSN_CLASS_A:
| ^~~~~~~~~~~~
| INSN_CLASS_H
../../binutils-gdb/sim/riscv/sim-main.c:1302:10: note: each undeclared identifier is reported only once for each function it appears in
Tom
prev parent reply other threads:[~2024-05-08 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 1:39 Nelson Chu
2024-05-08 4:37 ` Nelson Chu
2024-05-08 14:34 ` Tom Tromey [this message]
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=87o79g8j9s.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.com \
/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).