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>
Cc: binutils@sourceware.org
Subject: [PATCH 0/1] RISC-V: Fix RV32Q conflict
Date: Mon,  7 Feb 2022 12:31:48 +0900	[thread overview]
Message-ID: <cover.1644204639.git.research_trasio@irq.a4lg.com> (raw)

This commit allows combination of RV32 + 'Q' extension (IEEE 754
binary128 floating point number support).

This combination is no longer prohibited by the ISA Manual.

This restriction is introduced in binutils' RV32E support commit
7f99954970001cfc1b155d877ac2966d77e2c647.  At that time,
the latest ratified version of the RISC-V ISA Manual (version 2.2)
stated that 'Q' extension requires RV64IFD.

However, the next ratified version of the RISC-V ISA Manual
(20190608-Base-Ratified) removed such limitation.

I did check the version of 'Q' extension (RV32Q is allowed on 'Q'
extension version 2.2 or later) but it may be too pedant.

This is because  change (removal of RV64IFD dependency) seemed irrevant
to version changes but only a part of "embellishment" process as
described by riscv-isa-manual commit
013ba6dc8a504ee4ad7bee42554fecaef7ba797f.

Quoting preface of 20190608-Base-Ratified (would analogously to 'Q'),

> Incremented the version numbers of the F and D extensions to 2.2,
> reflecting that version 2.1 changed the canonical NaN, and version 2.2
> defined the NaN-boxing scheme and changed the definition of the FMIN
> and FMAX instructions.

Not checking the version number (just allowing RV32Q entirely) may be
an option.


References:

GNU Binutils:
  Commit 7f99954970001cfc1b155d877ac2966d77e2c647
    <https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=7f99954970001cfc1b155d877ac2966d77e2c647>

The RISC-V ISA Manual:
  version 2.2
    <https://github.com/riscv/riscv-isa-manual/releases?q=2.2>
  version 20190608-Base-Ratified
    <https://github.com/riscv/riscv-isa-manual/releases?q=Ratified-IMFDQC-and-Priv-v1.11>
  commit 013ba6dc8a504ee4ad7bee42554fecaef7ba797f:
    <https://github.com/riscv/riscv-isa-manual/commit/013ba6dc8a504ee4ad7bee42554fecaef7ba797f>




Tsukasa OI (1):
  RISC-V: Fix RV32Q conflict

 bfd/elfxx-riscv.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)


base-commit: 6a9d08661b361e497baa76dd6d8685f2cb593adb
-- 
2.32.0


             reply	other threads:[~2022-02-07  3:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07  3:31 Tsukasa OI [this message]
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   ` [PING][PATCH v2 0/1] " 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.1644204639.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@sourceware.org \
    /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).