From: Andrew Jones <ajones@ventanamicro.com>
To: Richard Bagley <rbagley@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com,
palmer@rivosinc.com, dbarboza@ventanamicro.com
Subject: Re: [PATCH] disas/riscv: Further correction to LUI disassembly
Date: Thu, 10 Aug 2023 17:31:46 +0200 [thread overview]
Message-ID: <20230810-c9e1f2783168b48bc07a1aa2@orel> (raw)
In-Reply-To: <20230731183320.410922-1-rbagley@ventanamicro.com>
On Mon, Jul 31, 2023 at 11:33:20AM -0700, Richard Bagley wrote:
> The recent commit 36df75a0a9 corrected one aspect of LUI disassembly
> by recovering the immediate argument from the result of LUI with a
> shift right by 12. However, the shift right will left-fill with the
> sign. By applying a mask we recover an unsigned representation of the
> 20-bit field (which includes a sign bit).
>
> Example:
> 0xfffff000 >> 12 = 0xffffffff
> 0xfffff000 >> 12 & 0xfffff = 0x000fffff
>
> Fixes: 36df75a0a9 ("riscv/disas: Fix disas output of upper immediates")
> Signed-off-by: Richard Bagley <rbagley@ventanamicro.com>
> ---
> disas/riscv.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/disas/riscv.c b/disas/riscv.c
> index 4023e3fc65..690eb4a1ac 100644
> --- a/disas/riscv.c
> +++ b/disas/riscv.c
> @@ -4723,9 +4723,12 @@ static void format_inst(char *buf, size_t buflen, size_t tab, rv_decode *dec)
> break;
> case 'U':
> fmt++;
> - snprintf(tmp, sizeof(tmp), "%d", dec->imm >> 12);
> - append(buf, tmp, buflen);
> - if (*fmt == 'o') {
> + if (*fmt == 'i') {
> + snprintf(tmp, sizeof(tmp), "%d", dec->imm >> 12 & 0xfffff);
Why are we correcting LUI's output, but still outputting sign-extended
values for AUIPC?
We can't assemble 'auipc a1, 0xffffffff' or 'auipc a1, -1' without getting
Error: lui expression not in range 0..1048575
(and additionally for 0xffffffff)
Error: value of 00000ffffffff000 too large for field of 4 bytes at 0000000000000000
either.
(I see that the assembler's error messages state 'lui', but I was trying
'auipc'.)
I'm using as from gnu binutils 2.40.0.20230214.
(And, FWIW, I agree with Richard Henderson that these instructions should
accept negative values.)
Thanks,
drew
> + append(buf, tmp, buflen);
> + } else if (*fmt == 'o') {
> + snprintf(tmp, sizeof(tmp), "%d", dec->imm >> 12);
> + append(buf, tmp, buflen);
> while (strlen(buf) < tab * 2) {
> append(buf, " ", buflen);
> }
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2023-08-10 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 18:33 [PATCH] disas/riscv: Further correction to LUI disassembly Richard Bagley
2023-07-31 20:37 ` Richard Henderson
2023-08-07 22:01 ` Richard Bagley
2023-08-07 22:59 ` Richard Henderson
2023-08-10 15:31 ` Andrew Jones [this message]
2023-08-10 16:12 ` Palmer Dabbelt
2023-08-10 16:27 ` Andrew Jones
2023-08-11 8:25 ` Andrew Jones
2023-08-11 11:55 ` Andrew Jones
2024-03-08 0:08 ` Richard Bagley
2024-03-09 4:22 ` Richard Bagley
2024-03-09 12:01 ` Andrew Jones
2024-03-11 18:56 ` Richard Bagley
2024-03-11 20:00 ` Richard Bagley
2024-03-12 11:09 ` Andrew Jones
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=20230810-c9e1f2783168b48bc07a1aa2@orel \
--to=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=palmer@rivosinc.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=rbagley@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.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 NNTP newsgroup(s).