From: Andrew Burgess <aburgess@redhat.com>
To: binutils@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Disassembler styling for ARM
Date: Fri, 16 Sep 2022 14:21:03 +0100 [thread overview]
Message-ID: <cover.1663334366.git.aburgess@redhat.com> (raw)
This series adds disassembler styling for ARM.
The first patch fixes what I believe is a missing comment marker (';')
in a couple of instructions.
The second patch adds styling support.
All thoughts and feedback welcome.
Thanks,
Andrew
---
Andrew Burgess (2):
opcodes/arm: add missing ';' characters
opcodes/arm: add disassembler styling for arm
.../testsuite/binutils-all/arm/objdump.exp | 4 +-
gas/testsuite/gas/arm/armv8.1-m.main-fp.d | 8 +-
gas/testsuite/gas/arm/vfp1xD.d | 16 +-
gas/testsuite/gas/arm/vfp1xD_t2.d | 8 +-
opcodes/arm-dis.c | 2628 ++++++++++-------
5 files changed, 1644 insertions(+), 1020 deletions(-)
--
2.25.4
next reply other threads:[~2022-09-16 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 13:21 Andrew Burgess [this message]
2022-09-16 13:21 ` [PATCH 1/2] opcodes/arm: add missing ';' characters Andrew Burgess
2022-09-20 15:13 ` Richard Earnshaw
2022-09-22 9:08 ` Andrew Burgess
2022-09-22 12:39 ` Richard Earnshaw
2022-09-22 18:20 ` Andrew Burgess
2022-09-16 13:21 ` [PATCH 2/2] opcodes/arm: add disassembler styling for arm Andrew Burgess
2022-10-02 10:47 ` [PATCHv2 0/2] Disassembler styling for ARM Andrew Burgess
2022-10-02 10:47 ` [PATCHv2 1/2] opcodes/arm: use '@' consistently for the comment character Andrew Burgess
2022-10-03 16:37 ` Andrew Burgess
2022-10-02 10:47 ` [PATCHv2 2/2] opcodes/arm: add disassembler styling for arm Andrew Burgess
2022-10-12 12:42 ` Andrew Burgess
2022-10-19 10:10 ` [PATCHv2 0/2] Disassembler styling for ARM Andrew Burgess
2022-10-31 14:59 ` Nick Clifton
2022-11-01 9:37 ` 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.1663334366.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).