From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Nelson Chu <nelson.chu@sifive.com>,
Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: [PATCH 0/2] RISC-V: Opcode Tidying - Operands (batch 1)
Date: Sun, 7 Aug 2022 17:00:20 +0900 [thread overview]
Message-ID: <cover.1659859212.git.research_trasio@irq.a4lg.com> (raw)
Hello,
This is a small patchset to clean / maintain RISC-V instruction operand types.
[PATCH 1/2]
Since `validate_riscv_insn' function lists three macro-only operand types, this
patch adds other three operands. That means, `validate_riscv_insn' lists all
macro-only operand types with this patch.
Existing:
- A
- B
- I
New in This Patch:
- c
- VM
- VT
Note that `validate_riscv_insn' is called only for non-macros. In the future,
we could reject (and make an internal error) when we encountered those macro-
only operand types on regular (non-macro) instructions.
[PATCH 2/2]
The operand type "b" has no good reasons to keep and should be removed.
- It looks like an alias of the "s" operand type.
- It hasn't used since the beginning.
- Its role is not clear.
On the other hand, this patch keeps following unused operand types for now:
- Cx : future compressed instructions?
- Vf, Ve : vector AMO instructions (instructions are not upstreamed
but operand types are upstreamed already)
- [, ] : used by some vendors? At least, their role is clear.
Thanks,
Tsukasa
Tsukasa OI (2):
RISC-V: Add macro-only operands to validate_riscv_insn
RISC-V: remove "b" operand type from disassembler
gas/config/tc-riscv.c | 3 +++
opcodes/riscv-dis.c | 1 -
2 files changed, 3 insertions(+), 1 deletion(-)
base-commit: 9663a947c09f63f75491dd4ad2f38fb448142240
--
2.34.1
next reply other threads:[~2022-08-07 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 8:00 Tsukasa OI [this message]
2022-08-07 8:00 ` [PATCH 1/2] RISC-V: Add macro-only operands to validate_riscv_insn Tsukasa OI
2022-08-07 8:00 ` [PATCH 2/2] RISC-V: remove "b" operand type from disassembler Tsukasa OI
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.1659859212.git.research_trasio@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=kito.cheng@sifive.com \
--cc=nelson.chu@sifive.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).