public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: binutils@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 0/2] PPC Styled Disassembler Support
Date: Mon, 18 Jul 2022 17:31:32 +0100	[thread overview]
Message-ID: <cover.1658161688.git.aburgess@redhat.com> (raw)
In-Reply-To: <20220712133609.3348690-1-aburgess@redhat.com>

Since v1:

  - Added patch #1, this is the exact same patch I'm proposing in my
    AArch64 thread; this adds dis_style_sub_mnemonic,

  - In patch #2, updated the formatting for things like '4*cr1+eq',
    the new styling is explained in the commit message,

  - Updated the styling of PPC_OPERAND_UDI operands to be register as
    suggested by Alan.

Thanks,
Andrew

---

Andrew Burgess (2):
  opcodes: add new sub-mnemonic disassembler style
  libopcodes/ppc: add support for disassembler styling

 binutils/objdump.c    |   2 +
 include/dis-asm.h     |   7 +++
 opcodes/disassemble.c |   1 +
 opcodes/ppc-dis.c     | 117 +++++++++++++++++++++++++++++++-----------
 4 files changed, 97 insertions(+), 30 deletions(-)

-- 
2.25.4


  parent reply	other threads:[~2022-07-18 16:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 13:36 [PATCH] libopcodes/ppc: add support for disassembler styling Andrew Burgess
2022-07-14  2:09 ` Alan Modra
2022-07-14  6:08   ` Jan Beulich
2022-07-14 11:18     ` Alan Modra
2022-07-18 16:31 ` Andrew Burgess [this message]
2022-07-18 16:31   ` [PATCHv2 1/2] opcodes: add new sub-mnemonic disassembler style Andrew Burgess
2022-07-18 16:31   ` [PATCHv2 2/2] libopcodes/ppc: add support for disassembler styling Andrew Burgess
2022-07-21  9:31     ` Alan Modra
2022-07-25 13:14       ` 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.1658161688.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).