public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Nelson Chu <nelson@rivosinc.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: [PATCH 0/5] RISC-V: Requirements for disassembler optimizations 1 (Tidying part)
Date: Sat,  8 Oct 2022 04:34:22 +0000	[thread overview]
Message-ID: <cover.1665203660.git.research_trasio@irq.a4lg.com> (raw)

Hello,

To improve the core disassembler (both for performance and feature), this
patchset now prepares for it.

This is the part 1 of (planned) 4 part patchsets.

1.  Tidying (you are here)
2.  Reorganization of the disassembler architecture
    (including some small optimizations)
3.  Optimization 1
4.  Optimization 2

Project:
<https://github.com/a4lg/binutils-gdb/wiki/proj_dis_perf_improvements_1>

Batch 1, Part 1 is the only hardly-functional part of the whole patchsets
and considered non-debatable.

-   Adds/fixes some comments
-   Fixes some formatting / typing
-   Removes/makes static some local variables

Again, this is mostly a tidying patchset.

Thanks,
Tsukasa




Tsukasa OI (5):
  opcodes/riscv-dis.c: Tidying with comments/clarity
  opcodes/riscv-dis.c: Tidying with spacing
  opcodes/riscv-dis.c: Use bool type whenever possible
  opcodes/riscv-dis.c: Make XLEN variable static
  opcodes/riscv-dis.c: Remove last_map_state

 opcodes/riscv-dis.c | 40 +++++++++++++++++++++++++++-------------
 1 file changed, 27 insertions(+), 13 deletions(-)


base-commit: 4cbfd0daabd68516651ee37a19d0e24ca4789ea3
-- 
2.34.1


             reply	other threads:[~2022-10-08  4:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08  4:34 Tsukasa OI [this message]
2022-10-08  4:34 ` [PATCH 1/5] opcodes/riscv-dis.c: Tidying with comments/clarity Tsukasa OI
2022-10-08  4:34 ` [PATCH 2/5] opcodes/riscv-dis.c: Tidying with spacing Tsukasa OI
2022-10-08  4:34 ` [PATCH 3/5] opcodes/riscv-dis.c: Use bool type whenever possible Tsukasa OI
2022-10-08  4:34 ` [PATCH 4/5] opcodes/riscv-dis.c: Make XLEN variable static Tsukasa OI
2022-10-08  4:34 ` [PATCH 5/5] opcodes/riscv-dis.c: Remove last_map_state Tsukasa OI
2022-10-14  3:47 ` [PATCH 0/5] RISC-V: Requirements for disassembler optimizations 1 (Tidying part) Nelson Chu

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.1665203660.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    --cc=kito.cheng@sifive.com \
    --cc=nelson@rivosinc.com \
    --cc=palmer@dabbelt.com \
    /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).