From: Nelson Chu <nelson@rivosinc.com>
To: gdb-patches@sourceware.org, Andrew Burgess <aburgess@redhat.com>
Subject: Fwd: [PATCH v2] RISC-V: Fix disassemble fetch fail return value.
Date: Tue, 21 Mar 2023 15:12:42 +0800 [thread overview]
Message-ID: <CAPpQWtCg7zHBfvDrmJp7=nMEf9+kGH_0p-qYVKOPZFbEOsL-XQ@mail.gmail.com> (raw)
In-Reply-To: <c06d0f96-eb16-484f-92ba-8b92551c5850.yunyao.zxl@alibaba-inc.com>
Hey gdb, Hey Andrew,
We plan to accept this patch in binutils upstream since it will fix
the pr30184, but not really sure if that will cause problems for
risc-v gdb dis-assembler, or other stuff. It would be great if you
guys also think it's safe enough to commit.
Thanks
Nelson
---------- Forwarded message ---------
From: Xiaolin Zheng <yunyao.zxl@alibaba-inc.com>
Date: Mon, Mar 20, 2023 at 1:52 PM
Subject: Re: [PATCH v2] RISC-V: Fix disassemble fetch fail return value.
To: Jiawei <jiawei@iscas.ac.cn>, binutils <binutils@sourceware.org>
Cc: nelson <nelson@rivosinc.com>, palmer <palmer@dabbelt.com>,
christoph.muellner <christoph.muellner@vrull.eu>, wuwei2016
<wuwei2016@iscas.ac.cn>
Thank you Jiawei. this version LGTM though I am not a Binutils
developer. Do Binutils reviewers have thoughts on this new version?
Thanks in advance.
------------------------------------------------------------------
From:Jiawei <jiawei@iscas.ac.cn>
Send Time:2023年3月20日(星期一) 11:35
To:binutils <binutils@sourceware.org>
Cc:nelson <nelson@rivosinc.com>; palmer <palmer@dabbelt.com>;
christoph.muellner <christoph.muellner@vrull.eu>; 郑孝林(云矅)
<yunyao.zxl@alibaba-inc.com>; wuwei2016 <wuwei2016@iscas.ac.cn>;
Jiawei <jiawei@iscas.ac.cn>
Subject:[PATCH v2] RISC-V: Fix disassemble fetch fail return value.
This bug reported in
https://sourceware.org/bugzilla/show_bug.cgi?id=30184
And discussed in
https://sourceware.org/pipermail/binutils/2023-February/126213.html
We also checked the implementation of return value in arm and mips.
So this patch changes the return value to -1, that can fix bugs and maintain
consistency with other architectures.
opcodes/ChangeLog:
* riscv-dis.c (print_insn_riscv):Change the return value.
---
opcodes/riscv-dis.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/opcodes/riscv-dis.c b/opcodes/riscv-dis.c
index 7baba054daa..f431124b423 100644
--- a/opcodes/riscv-dis.c
+++ b/opcodes/riscv-dis.c
@@ -1059,7 +1059,7 @@ print_insn_riscv (bfd_vma memaddr, struct
disassemble_info *info)
if (status != 0)
{
(*info->memory_error_func) (status, memaddr, info);
- return status;
+ return -1;
}
insn = (insn_t) bfd_getl16 (packet);
dump_size = riscv_insn_length (insn);
@@ -1071,7 +1071,7 @@ print_insn_riscv (bfd_vma memaddr, struct
disassemble_info *info)
if (status != 0)
{
(*info->memory_error_func) (status, memaddr, info);
- return status;
+ return -1;
}
insn = (insn_t) bfd_get_bits (packet, dump_size * 8, false);
--
2.25.1
next parent reply other threads:[~2023-03-21 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230320033444.2819-1-jiawei@iscas.ac.cn>
[not found] ` <c06d0f96-eb16-484f-92ba-8b92551c5850.yunyao.zxl@alibaba-inc.com>
2023-03-21 7:12 ` Nelson Chu [this message]
2023-03-21 9:22 ` Andrew Burgess
2023-03-21 9:55 ` Nelson Chu
2023-03-21 10:14 ` Xiaolin Zheng
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='CAPpQWtCg7zHBfvDrmJp7=nMEf9+kGH_0p-qYVKOPZFbEOsL-XQ@mail.gmail.com' \
--to=nelson@rivosinc.com \
--cc=aburgess@redhat.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).