public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: mengqinggang <mengqinggang@loongson.cn>
To: binutils@sourceware.org, i.swmail@xen0n.name
Cc: xuchenghua@loongson.cn, liuzhensong@loongson.cn,
	Xi Ruoyao <xry111@xry111.site>
Subject: [PATCH v2 0/5] LoongArch: colored disassembly and readability tweaks
Date: Tue, 13 Dec 2022 16:09:50 +0800	[thread overview]
Message-ID: <8ecae091-714e-8045-0bdf-a1580a198a10@loongson.cn> (raw)

This series patches result in some gas/ld test errors. There are some
files need to be regenerated.

Could you please add me to CC list in future email, thanks.


Hi,

This series implements colored output for LoongArch disassembly, and
some minor tweaks to the output so there is less clutter.

The previous version was sent in August but there was no reply, so I've
rebased and added the tweaks mentioned before, for consideration of
inclusion into binutils 2.40.

WANG Xuerui (5):
   opcodes/loongarch: remove unused code
   opcodes/loongarch: implement style support in the disassembler
   opcodes/loongarch: style disassembled address offsets as such
   opcodes/loongarch: do not print hex notation for signed immediates
   opcodes/loongarch: print unrecognized instruction words with .insn
     prefix

  include/opcode/loongarch.h |  5 ---
  opcodes/disassemble.c      |  5 +++
  opcodes/loongarch-dis.c    | 88 ++++++++++++++------------------------
  opcodes/loongarch-opc.c    | 50 +++++++++++-----------
  4 files changed, 62 insertions(+), 86 deletions(-)


             reply	other threads:[~2022-12-13  8:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13  8:09 mengqinggang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-07 13:31 WANG Xuerui

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=8ecae091-714e-8045-0bdf-a1580a198a10@loongson.cn \
    --to=mengqinggang@loongson.cn \
    --cc=binutils@sourceware.org \
    --cc=i.swmail@xen0n.name \
    --cc=liuzhensong@loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).