From: Nelson Chu <nelson@rivosinc.com>
To: Charlie Jenkins <charlie@rivosinc.com>
Cc: Andreas Schwab <schwab@suse.de>,
Andrew Burgess <aburgess@redhat.com>,
Soham Gargote <sgargote@whileone.in>,
gdb-patches@sourceware.org, binutils@sourceware.org,
Sameer Natu <snatu@whileone.in>
Subject: Re: [PATCH] Set rv64gcv as default to enable vector extension for disassembly
Date: Thu, 31 Jul 2025 18:32:59 +0800 [thread overview]
Message-ID: <CAPpQWtCwh9vV9qfQr1nq-TEkQB+ksY1vw146FvwoFMdu9fVykw@mail.gmail.com> (raw)
In-Reply-To: <aIsZXlQvgXu10D3z@ghost>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
On Thu, Jul 31, 2025 at 3:21 PM Charlie Jenkins <charlie@rivosinc.com>
wrote:
> On Thu, Jul 31, 2025 at 10:37:16AM +0800, Nelson Chu wrote:
> > On Wed, Jul 30, 2025 at 9:09 PM Andreas Schwab <schwab@suse.de> wrote:
> >
> > > Why is that needed? AFAICT, objdump will happily decode any extension
> > > without that change.
> > >
> >
> > I guess maybe they are trying to dump an object which writes
> > vector instructions by .insn directives, so the elf architecture
> attribute
> > or mapping symbols won't have v. I will suggest two solutions here
> rather
>
> The goal here is to be able to use the disassembler from inside of
> native riscv gdb to dump any instruction. Currently it seems like gdb
> will only dump a subset of all instructions, even with the patch you
> sent Nelson. Here is an example program:
>
My patch isn't used to resolve your problem, it just lets assembler and
dis-assembler have the same default arch, so people can just update
riscv_all_supported_ext. It's probably convenient to be maintained.
Nelson
[-- Attachment #2: Type: text/html, Size: 1584 bytes --]
next prev parent reply other threads:[~2025-07-31 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 10:40 Soham Gargote
2025-07-30 12:27 ` Andrew Burgess
2025-07-30 13:07 ` Andreas Schwab
2025-07-31 2:37 ` Nelson Chu
2025-07-31 7:21 ` Charlie Jenkins
2025-07-31 7:33 ` Jan Beulich
2025-07-31 10:32 ` Nelson Chu [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-22 10:34 Soham Gargote
2025-07-22 19:42 ` Andrew Burgess
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=CAPpQWtCwh9vV9qfQr1nq-TEkQB+ksY1vw146FvwoFMdu9fVykw@mail.gmail.com \
--to=nelson@rivosinc.com \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=charlie@rivosinc.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@suse.de \
--cc=sgargote@whileone.in \
--cc=snatu@whileone.in \
/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