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/1] RISC-V psABI: Add testcase for DWARF register numbers
Date: Fri, 23 Sep 2022 08:41:44 +0000 [thread overview]
Message-ID: <cover.1663922476.git.research_trasio@irq.a4lg.com> (raw)
Hello,
This is based on the subset of
"RISC-V psABI: Assign DWARF register numbers to vector registers"
<https://sourceware.org/pipermail/binutils/2022-September/123007.html>.
Although it had csr-dw-regnums.d to test DWARF register numbers for CSRs,
it didn't have DWARF register number test for GPRs/FPRs.
So, this patchset adds it.
The reason I split this (from vector register patchset) is these register
numbers for GPRs/FPRs are widely accepted already and adding this test first
makes possible to completely split vector register patchset and the DWARF
register number test itself.
I also made a change so that we test "fp" (alias of "x8" or "s0"; I forgot
to add this to the test).
Thanks,
Tsukasa
Tsukasa OI (1):
RISC-V: Add testcase for DWARF register numbers
gas/testsuite/gas/riscv/dw-regnums.d | 149 ++++++++++++++++++++++++++
gas/testsuite/gas/riscv/dw-regnums.s | 151 +++++++++++++++++++++++++++
2 files changed, 300 insertions(+)
create mode 100644 gas/testsuite/gas/riscv/dw-regnums.d
create mode 100644 gas/testsuite/gas/riscv/dw-regnums.s
base-commit: 8e037eae6823caf5b9cb5b4feb3de838abb25956
--
2.34.1
next reply other threads:[~2022-09-23 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 8:41 Tsukasa OI [this message]
2022-09-23 8:41 ` [PATCH 1/1] RISC-V: " Tsukasa OI
2022-10-08 4:29 ` [PATCH v2 0/1] RISC-V psABI: Add testcase for DWARF register numbers (supplemental) Tsukasa OI
2022-10-08 4:29 ` [PATCH v2 1/1] RISC-V: Test DWARF register numbers for "fp" Tsukasa OI
2022-10-14 1:33 ` [PATCH v2 0/1] RISC-V psABI: Add testcase for DWARF register numbers (supplemental) 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.1663922476.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).