From: Andrew Burgess <aburgess@redhat.com>
To: binutils@sourceware.org
Subject: Re: [PATCH 0/2] MIPS disassembler styling
Date: Mon, 28 Nov 2022 17:15:15 +0000 [thread overview]
Message-ID: <87v8mz0zmk.fsf@redhat.com> (raw)
In-Reply-To: <cover.1667483581.git.aburgess@redhat.com>
Ping!
Thanks,
Andrew
Andrew Burgess <aburgess@redhat.com> writes:
> This commit adds disassembler styling for MIPS.
>
> Patch 1/2 changes the disassembler to make use of the assembler
> directives .word and .short. This isn't a requirement, but I think is
> an improvement. There's a lot of updated tests in this commit, it's
> possible that this patch might be too large to reach the mailing list.
> In case of this, I've pushed my work to the branch:
> users/aburgess/try-mips-disasm-styling
>
> Patch 2/2 is where I actually add disassembler styling. If patch #1
> is not wanted then I can easily rebase this second patch, removing the
> use of .word and .short, just let me know.
>
> Thanks,
> Andrew
>
> ---
>
> Andrew Burgess (2):
> opcodes/mips: use .word/.short for undefined instructions
> libopcodes/mips: add support for disassembler styling
>
> .../testsuite/binutils-all/mips/mips-ase-1.d | 2 +-
> .../binutils-all/mips/mips-xpa-virt-1.d | 4 +-
> .../binutils-all/mips/mips-xpa-virt-2.d | 4 +-
> .../binutils-all/mips/mips-xpa-virt-3.d | 2 +-
> .../binutils-all/mips/mips1-branch-alias.d | 4 +-
> .../binutils-all/mips/mips1-branch-noalias.d | 4 +-
> .../binutils-all/mips/mips16-extend-noinsn.d | 24 +-
> .../binutils-all/mips/mips16-pcrel.d | 16 +-
> .../binutils-all/mips/mips32r6-branch-alias.d | 4 +-
> .../mips/mips32r6-branch-noalias.d | 4 +-
> gas/testsuite/gas/mips/interaptiv-mr2@mcu.d | 112 ++---
> .../gas/mips/mips16-32@mips16-asmacro.d | 6 +-
> gas/testsuite/gas/mips/mips16-32@mips16-sub.d | 436 +++++++++---------
> .../gas/mips/mips16-32@mips16e-64-sub.d | 4 +-
> .../gas/mips/mips16-32@mips16e-sub.d | 66 +--
> gas/testsuite/gas/mips/mips16@save-sub.d | 68 +--
> gas/testsuite/gas/mips/mips1@isa-override-1.d | 16 +-
> gas/testsuite/gas/mips/mips1@save-sub.d | 68 +--
> gas/testsuite/gas/mips/mips2@isa-override-1.d | 12 +-
> .../gas/mips/mips32@isa-override-1.d | 14 +-
> .../gas/mips/mips32r2@isa-override-1.d | 14 +-
> gas/testsuite/gas/mips/set-arch.d | 208 ++++-----
> gas/testsuite/gas/mips/tls-o32.d | 4 +-
> opcodes/disassemble.c | 5 +
> opcodes/mips-dis.c | 306 +++++++-----
> 25 files changed, 751 insertions(+), 656 deletions(-)
>
> --
> 2.25.4
next prev parent reply other threads:[~2022-11-28 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 13:58 Andrew Burgess
2022-11-03 13:58 ` [PATCH 1/2] opcodes/mips: use .word/.short for undefined instructions Andrew Burgess
2023-01-06 15:58 ` Maciej W. Rozycki
2023-01-06 16:40 ` Andrew Burgess
2023-01-08 16:05 ` Maciej W. Rozycki
2023-01-17 10:28 ` Andrew Burgess
2023-01-27 11:57 ` Maciej W. Rozycki
2023-01-30 9:34 ` Andrew Burgess
2023-02-01 10:40 ` Maciej W. Rozycki
2023-02-01 15:32 ` Andrew Burgess
2023-02-02 9:48 ` Maciej W. Rozycki
2023-02-03 9:31 ` Andrew Burgess
2023-02-13 12:07 ` Andrew Burgess
2023-02-14 4:43 ` Maciej W. Rozycki
2022-11-03 13:58 ` [PATCH 2/2] libopcodes/mips: add support for disassembler styling Andrew Burgess
2022-11-28 17:15 ` Andrew Burgess [this message]
2022-11-30 16:50 ` [PATCH 0/2] MIPS " Nick Clifton
2022-12-05 10:08 ` 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=87v8mz0zmk.fsf@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).