public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Nick Clifton <nickc@redhat.com>,
	Andrew Burgess <aburgess@redhat.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: [PATCH v2 0/2] gdb, opcodes: Add non-enum disassembler options
Date: Sun,  4 Sep 2022 08:03:18 +0000	[thread overview]
Message-ID: <cover.1662278591.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1661912099.git.research_trasio@irq.a4lg.com>

Hello,

This is a part of my work: implement `arch' disassembler option in RISC-V.
However, it requires technical changes also affecting opcodes:ARC and MIPS
and GDB.  It will take some time because we have to wait many Binutils
prerequisites but this technical change can be discussed now (due to it
affects both Binutils and GDB).

PATCH v1
    <https://sourceware.org/pipermail/binutils/2022-August/122677.html>
    <https://sourceware.org/pipermail/gdb-patches/2022-August/191611.html>
... is approved as follows:

PATCH 1/2: Binutils changes
    <https://sourceware.org/pipermail/binutils/2022-September/122697.html> (2022-09-01)
PATCH 2/2: GDB changes
    <https://sourceware.org/pipermail/gdb-patches/2022-September/191668.html> (2022-09-02)

The code part of PATCH v2 is unchanged from (approved) PATCH v1 but minor
commit message issues (including excess ChangeLog and quoting) are fixed.

Since I don't have write access yet, it's my preasure to merge the commits
if approved.

Thanks,
Tsukasa




Tsukasa OI (2):
  opcodes: Add non-enum disassembler options
  gdb: Add non-enum disassembler options

 gdb/disasm.c        | 4 ++++
 include/dis-asm.h   | 3 ++-
 opcodes/arc-dis.c   | 2 ++
 opcodes/mips-dis.c  | 2 ++
 opcodes/riscv-dis.c | 2 ++
 5 files changed, 12 insertions(+), 1 deletion(-)


base-commit: 148b68a56c57d69bd97a5f40c34fc4700693596a
-- 
2.34.1


  parent reply	other threads:[~2022-09-04  8:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  2:15 [PATCH " Tsukasa OI
2022-08-31  2:15 ` [PATCH 1/2] " Tsukasa OI
2022-09-01 12:03   ` Nick Clifton
2022-08-31  2:15 ` [PATCH 2/2] gdb: " Tsukasa OI
2022-09-02 10:00   ` Andrew Burgess
2022-09-04  8:03 ` Tsukasa OI [this message]
2022-09-04  8:03   ` [PATCH v2 1/2] opcodes: " Tsukasa OI
2022-09-06  2:36     ` Tsukasa OI
2022-09-06  8:31       ` Tsukasa OI
2022-09-04  8:03   ` [PATCH v2 2/2] gdb: " 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.1662278591.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=aburgess@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).