From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>
Cc: binutils@sourceware.org
Subject: [RFC PATCH v2 0/2] gdb, opcodes: Add isa disassembler option to RISC-V
Date: Sun, 6 Feb 2022 11:10:35 +0900 [thread overview]
Message-ID: <cover.1644113385.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1644056624.git.research_trasio@irq.a4lg.com>
*** NOTE ***
PATCH 1 contains non-RISC-V (GDB-related) changes.
This patchset adds support for isa=ISA diassembler option to RISC-V.
- objdump: -M isa=rv[32|64]...
- gdb: set disassembler-options isa=rv[32|64]...
This patchset is version 2. Version 1 is here:
<https://sourceware.org/pipermail/binutils/2022-February/119639.html>
<https://github.com/a4lg/binutils-gdb/tree/a4lg/snapshots/2022-02-05/riscv-dis-isa>
My development branch on GitHub:
<https://github.com/a4lg/binutils-gdb/tree/riscv-dis-isa>
[Changes between RFC PATCH v1 and RFC PATCH v2]
The only functional change in the RFC PATCH v2 is that we reset `xlen'
variable to `0' before parsing ISA string. It has no effect on objdump
but on GDB, it stops preserving last XLEN value before setting invalid
ISA string (not starting with "rv32" or "rv64").
Rest of the changes are editorial. My language got broken while writing
v1 but I think most of them are fixed in v2. Also, most "-M isa"
(objdump-only) references are replaced with just "isa" to indicate
both objdump and GDB options.
Renamed `xlen_set_by_option' to `xlen_by_isa' for clarity (meaning XLEN
set by "ISA string" option).
Tsukasa OI (2):
gdb, opcodes: Add non-enum disassembler options
RISC-V: Add isa disassembler option
gdb/disasm.c | 4 ++++
include/dis-asm.h | 3 ++-
opcodes/arc-dis.c | 2 ++
opcodes/mips-dis.c | 2 ++
opcodes/riscv-dis.c | 35 ++++++++++++++++++++++++++++-------
5 files changed, 38 insertions(+), 8 deletions(-)
base-commit: 94e57f287f96af6af97dd086e4a04ddf55b7cf60
--
2.32.0
next prev parent reply other threads:[~2022-02-06 2:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 10:24 [RFC PATCH 0/2] gdb, opcodes: Add -M " Tsukasa OI
2022-02-05 10:24 ` [RFC PATCH 1/2] gdb, opcodes: Add non-enum disassembler options Tsukasa OI
2022-02-05 10:24 ` [RFC PATCH 2/2] RISC-V: Add -M isa disassembler option Tsukasa OI
2022-02-24 18:00 ` Palmer Dabbelt
2022-02-06 2:10 ` Tsukasa OI [this message]
2022-02-06 2:10 ` [RFC PATCH v2 1/2] gdb, opcodes: Add non-enum disassembler options Tsukasa OI
2022-02-06 2:10 ` [RFC PATCH v2 2/2] RISC-V: Add isa disassembler option Tsukasa OI
2022-02-07 6:47 ` [RFC PATCH v2 0/2] gdb, opcodes: Add isa disassembler option to RISC-V Nelson Chu
2022-02-07 9:58 ` Tsukasa OI
2022-02-07 10:06 ` Kito Cheng
2022-02-07 10:19 ` Tsukasa OI
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=cover.1644113385.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@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).