public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Andrew Burgess via Binutils <binutils@sourceware.org>,
	binutils@sourceware.org
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Subject: Re: [PATCHv5 1/2] opcodes: add new sub-mnemonic disassembler style
Date: Mon, 25 Jul 2022 14:34:41 +0100	[thread overview]
Message-ID: <87a68x9uz2.fsf@redhat.com> (raw)
In-Reply-To: <d38704f9a19eb6455c9f90be909f71cb2091aa6f.1658393015.git.aburgess@redhat.com>

Andrew Burgess via Binutils <binutils@sourceware.org> writes:

> When adding libopcodes disassembler styling support for AArch64, it
> feels like the results would be improved by having a new sub-mnemonic
> style.  This will be used in cases like:
>
>   add    w16, w7, w1, uxtb #2
>                       ^^^^----- Here
>
> And:
>
>   cinc   w0, w1, ne
>                  ^^----- Here
>
> This commit just adds the new style, and prepares objdump to handle
> the style.  A later commit will add AArch64 styling, and will actually
> make use of the style.
>
> As this style is currently unused, there should be no user visible
> changes after this commit.

The dis_style_sub_mnemonic style has now been merged upstream as part of
the ppc styling patches.  The other patch in this series still needs
approval.

Thanks,
Andrew



> ---
>  binutils/objdump.c | 2 ++
>  include/dis-asm.h  | 7 +++++++
>  2 files changed, 9 insertions(+)
>
> diff --git a/binutils/objdump.c b/binutils/objdump.c
> index 67824053527..4076587151c 100644
> --- a/binutils/objdump.c
> +++ b/binutils/objdump.c
> @@ -2167,6 +2167,7 @@ objdump_color_for_disassembler_style (enum disassembler_style style)
>  	{
>  	case dis_style_symbol: color = 32; break;
>          case dis_style_assembler_directive:
> +	case dis_style_sub_mnemonic:
>  	case dis_style_mnemonic: color = 33; break;
>  	case dis_style_register: color = 34; break;
>  	case dis_style_address:
> @@ -2185,6 +2186,7 @@ objdump_color_for_disassembler_style (enum disassembler_style style)
>  	{
>  	case dis_style_symbol: color = 40; break;
>          case dis_style_assembler_directive:
> +	case dis_style_sub_mnemonic:
>  	case dis_style_mnemonic: color = 142; break;
>  	case dis_style_register: color = 27; break;
>  	case dis_style_address:
> diff --git a/include/dis-asm.h b/include/dis-asm.h
> index 4f91df12498..f1a83dc84e5 100644
> --- a/include/dis-asm.h
> +++ b/include/dis-asm.h
> @@ -62,6 +62,13 @@ enum disassembler_style
>       instructions.  */
>    dis_style_mnemonic,
>  
> +  /* Some architectures include additional mnemonic like fields within the
> +     instruction operands, e.g. on aarch64 'add w16, w7, w1, lsl #2' where
> +     the 'lsl' is an additional piece of text that describes how the
> +     instruction should behave.  This sub-mnemonic style can be used for
> +     these pieces of text.  */
> +  dis_style_sub_mnemonic,
> +
>    /* For things that aren't real machine instructions, but rather
>       assembler directives, e.g. .byte, etc.  */
>    dis_style_assembler_directive,
> -- 
> 2.25.4


  reply	other threads:[~2022-07-25 13:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 11:22 [PATCH 0/2] AArch64 libopcodes styling Andrew Burgess
2022-06-21 11:22 ` [PATCH 1/2] opcodes/aarch64: split off creation of comment text in disassembler Andrew Burgess
2022-06-22 11:02   ` Nick Clifton
2022-06-29 11:19     ` Andrew Burgess
2022-06-21 11:22 ` [PATCH 2/2] libopcodes/aarch64: add support for disassembler styling Andrew Burgess
2022-06-22 11:15   ` Nick Clifton
2022-06-29 11:01     ` Andrew Burgess
2022-06-29 11:12       ` Jan Beulich
2022-06-29 12:36   ` Richard Earnshaw
2022-07-04  9:52   ` Nick Clifton
2022-07-05 12:45 ` [PATCHv2 0/2] AArch64 libopcodes styling Andrew Burgess
2022-07-05 12:46   ` [PATCHv2 1/2] opcodes: add new sub-mnemonic disassembler style Andrew Burgess
2022-07-05 12:46   ` [PATCHv2 2/2] libopcodes/aarch64: add support for disassembler styling Andrew Burgess
2022-07-05 12:51     ` Andrew Burgess
2022-07-05 13:10       ` Richard Earnshaw
2022-07-07 10:23         ` [PATCHv3 0/2] AArch64 libopcodes styling Andrew Burgess
2022-07-07 10:23           ` [PATCHv3 1/2] opcodes: add new sub-mnemonic disassembler style Andrew Burgess
2022-07-07 10:23           ` [PATCHv3 2/2] libopcodes/aarch64: add support for disassembler styling Andrew Burgess
2022-07-07 10:44             ` Andrew Burgess
2022-07-08 10:25           ` [PATCHv4 0/2] AArch64 libopcodes styling Andrew Burgess
2022-07-08 10:25             ` [PATCHv4 1/2] opcodes: add new sub-mnemonic disassembler style Andrew Burgess
2022-07-26 13:54               ` Nick Clifton
2022-07-08 10:25             ` [PATCHv4 2/2] libopcodes/aarch64: add support for disassembler styling Andrew Burgess
2022-07-19 15:33               ` Richard Earnshaw
2022-07-21  8:56                 ` [PATCHv5 0/2] AArch64 libopcodes styling Andrew Burgess
2022-07-21  8:56                   ` [PATCHv5 1/2] opcodes: add new sub-mnemonic disassembler style Andrew Burgess
2022-07-25 13:34                     ` Andrew Burgess [this message]
2022-07-21  8:56                   ` [PATCHv5 2/2] libopcodes/aarch64: add support for disassembler styling Andrew Burgess
2022-07-26 13:55                     ` Nick Clifton
2022-07-29 13:12                       ` Andrew Burgess
2022-07-19 12:52             ` [PATCHv4 0/2] AArch64 libopcodes styling 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=87a68x9uz2.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=Richard.Earnshaw@foss.arm.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).