From: Andrew Burgess <aburgess@redhat.com>
To: binutils@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] RISC-V styled disassembler output fixes
Date: Wed, 5 Jun 2024 13:21:39 +0100 [thread overview]
Message-ID: <cover.1717589992.git.aburgess@redhat.com> (raw)
A recent(ish) commit added some non-styled output to the RISC-V
disassembler.
In the first patch I convert the non-styled output to be styled.
In the second patch I attempt to add a mechanism that will prevent
such code being introduced in the future.
Thanks,
Andrew
---
Andrew Burgess (2):
opcodes/riscv: add styling support to print_reg_list
opcodes/riscv: prevent future use of disassemble_info::fprintf_func
opcodes/riscv-dis.c | 56 +++++++++++++++++++++++++++++++++------------
1 file changed, 42 insertions(+), 14 deletions(-)
base-commit: f95540d91f4c3df373c0f9e212030154658d7f6f
--
2.25.4
next reply other threads:[~2024-06-05 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 12:21 Andrew Burgess [this message]
2024-06-05 12:21 ` [PATCH 1/2] opcodes/riscv: add styling support to print_reg_list Andrew Burgess
2024-06-05 12:21 ` [PATCH 2/2] opcodes/riscv: prevent future use of disassemble_info::fprintf_func Andrew Burgess
2024-06-06 1:01 ` [PATCH 0/2] RISC-V styled disassembler output fixes Nelson Chu
2024-06-06 9:35 ` 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=cover.1717589992.git.aburgess@redhat.com \
--to=aburgess@redhat.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).