From: Charlie Jenkins <charlie@rivosinc.com>
To: jiawei <jiawei@iscas.ac.cn>, Nelson Chu <nelson@rivosinc.com>,
Charlie Jenkins <charlie@rivosinc.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: [PATCH 0/2] RISC-V: Fix abort when displaying data and add test
Date: Tue, 11 Feb 2025 21:08:29 -0800 [thread overview]
Message-ID: <20250211-fix_gas_abort-v1-0-afd9730f9c51@rivosinc.com> (raw)
Commit 6a04e8230707 ("RISC-V: Fix display of partial instructions")
changed how objdump displays instructions. This had the unintented
side-effect that it allowed 6 byte instructions to be displayed which
happens when a .dword is attempted to be split into instructions. Add
support for 5, 6, and 7 byte instructions to remedy this
issue.
Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
---
Charlie Jenkins (2):
RISC-V: Fix abort when displaying .dword
RISC-V: Add testcase for 6 byte instruction
gas/testsuite/gas/riscv/dis-partial-insn-dword.d | 12 ++++++++++
gas/testsuite/gas/riscv/dis-partial-insn-dword.s | 2 ++
opcodes/riscv-dis.c | 29 +++++++++++++++++++++++-
3 files changed, 42 insertions(+), 1 deletion(-)
---
base-commit: 815d9a14cbbb3b81843f7566222c87fb22e7255d
change-id: 20250211-fix_gas_abort-6d1e28b4ad46
--
- Charlie
next reply other threads:[~2025-02-12 5:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 5:08 Charlie Jenkins [this message]
2025-02-12 5:08 ` [PATCH 1/2] RISC-V: Fix abort when displaying .dword Charlie Jenkins
2025-02-12 5:27 ` Jiawei
2025-02-12 7:25 ` Alan Modra
2025-02-12 8:06 ` Jan Beulich
2025-02-12 8:57 ` Nelson Chu
2025-02-12 10:06 ` Jan Beulich
2025-02-12 22:15 ` Maciej W. Rozycki
2025-02-13 0:51 ` Charlie Jenkins
2025-02-13 0:52 ` Charlie Jenkins
2025-02-12 5:08 ` [PATCH 2/2] RISC-V: Add testcase for 6 byte instruction Charlie Jenkins
2025-02-12 5:20 ` [PATCH 0/2] RISC-V: Fix abort when displaying data and add test Nelson Chu
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=20250211-fix_gas_abort-v1-0-afd9730f9c51@rivosinc.com \
--to=charlie@rivosinc.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jiawei@iscas.ac.cn \
--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