From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Kito Cheng <kito.cheng@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>
Subject: [PING][PATCH v2 0/1] RISC-V: Fix RV32Q conflict
Date: Tue, 24 May 2022 18:48:53 +0900 [thread overview]
Message-ID: <9c9d505f-98e2-43fa-8e45-892aa2357bbd@irq.a4lg.com> (raw)
In-Reply-To: <cover.1645951855.git.research_trasio@irq.a4lg.com>
On 2022/02/27 17:51, Tsukasa OI wrote:
> [v2]
>
> This commit allows combination of RV32 + 'Q' extension (IEEE 754
> binary128 floating point number support), version 2.2 or later.
>
> This combination is no longer prohibited by the specification.
>
> v1:
> <https://sourceware.org/pipermail/binutils/2022-February/119655.html>
>
> Changes: v1 -> v2
> - Changed/renamed testcase so that no failure occurs.
> RV32IQ with old ISA (version 2.2 w/ 'Q' 2.0) is prohibited.
> - Added testcase so that RV32IQ with recent ISA succeeds.
> RV32IQ with new ISA (version 20190608 w/ 'Q' 2.2) is allowed.
> - Added testcases for RV32I + 'Q' per extension version
> - 'Q' extension version 2.0 with RV32I is prohibited.
> ("rv32iq2" means RV32I + Q version 2".0" so also prohibited.)
> - 'Q' extension version 2.2 with RV32I is allowed.
>
> As I noted in v1, this implementation might be too pedantic.
> An option is to allow RV32IQ entirely (regardless of version numbers).
>
>
>
>
> Tsukasa OI (1):
> RISC-V: Fix RV32Q conflict
>
> bfd/elfxx-riscv.c | 5 +++--
> gas/testsuite/gas/riscv/march-fail-rv32iq-isa-2p2.d | 3 +++
> gas/testsuite/gas/riscv/march-fail-rv32iq.d | 3 ---
> gas/testsuite/gas/riscv/march-fail-rv32iq2.d | 3 +++
> gas/testsuite/gas/riscv/march-fail-rv32iq2p0.d | 3 +++
> .../riscv/{march-fail-rv32iq.l => march-fail-rv32iq2p0.l} | 0
> gas/testsuite/gas/riscv/march-ok-rv32iq-isa-20190608.d | 5 +++++
> gas/testsuite/gas/riscv/march-ok-rv32iq2p2.d | 5 +++++
> 8 files changed, 22 insertions(+), 5 deletions(-)
> create mode 100644 gas/testsuite/gas/riscv/march-fail-rv32iq-isa-2p2.d
> delete mode 100644 gas/testsuite/gas/riscv/march-fail-rv32iq.d
> create mode 100644 gas/testsuite/gas/riscv/march-fail-rv32iq2.d
> create mode 100644 gas/testsuite/gas/riscv/march-fail-rv32iq2p0.d
> rename gas/testsuite/gas/riscv/{march-fail-rv32iq.l => march-fail-rv32iq2p0.l} (100%)
> create mode 100644 gas/testsuite/gas/riscv/march-ok-rv32iq-isa-20190608.d
> create mode 100644 gas/testsuite/gas/riscv/march-ok-rv32iq2p2.d
>
>
> base-commit: b275570803cefba388595bc42b75b68403eb86f1
Let me allow to send a ping.
Original:
https://sourceware.org/pipermail/binutils/2022-February/119893.html
I completely understand that my other fixes (except this and
Zihintpause) are relatively large and needs some time to review.
I think this (and Zihintpause patch) are completely safe to merge.
Thanks,
Tsukasa
prev parent reply other threads:[~2022-05-24 9:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 3:31 [PATCH " Tsukasa OI
2022-02-07 3:31 ` [PATCH 1/1] " Tsukasa OI
2022-02-07 7:48 ` [PATCH 0/1] " Jan Beulich
2022-02-07 10:17 ` Tsukasa OI
2022-02-27 8:51 ` [PATCH v2 " Tsukasa OI
2022-02-27 8:51 ` [PATCH v2 1/1] " Tsukasa OI
2022-05-24 12:04 ` Kito Cheng
2022-05-25 3:23 ` Nelson Chu
2022-05-24 9:48 ` Tsukasa OI [this message]
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=9c9d505f-98e2-43fa-8e45-892aa2357bbd@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).