From: Andreas Schwab <schwab@suse.de>
To: Andrew Burgess <aburgess@redhat.com>
Cc: 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: Wed, 30 Jul 2025 15:07:19 +0200 [thread overview]
Message-ID: <mvmseidx1x4.fsf@suse.de> (raw)
In-Reply-To: <87a54ldftg.fsf@redhat.com> (Andrew Burgess's message of "Wed, 30 Jul 2025 13:27:23 +0100")
Why is that needed? AFAICT, objdump will happily decode any extension
without that change.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2025-07-30 13:07 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 [this message]
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
-- 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=mvmseidx1x4.fsf@suse.de \
--to=schwab@suse.de \
--cc=aburgess@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--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