RISC-V: Remove RV32EF conflict
authorTsukasa OI <research_trasio@irq.a4lg.com>
Sat, 10 Sep 2022 08:32:17 +0000 (08:32 +0000)
committerTsukasa OI <research_trasio@irq.a4lg.com>
Mon, 7 Nov 2022 04:44:34 +0000 (04:44 +0000)
commit092a151a38c1bd87f25d1d03d4089a25b1bfbbc8
treedbfedca176fb0c99c141aedb9373984b24f1ce56
parent2f008f0640923fa307fdd73b229f951e64a1574b
RISC-V: Remove RV32EF conflict

Despite that the RISC-V ISA Manual version 2.2 prohibited "RV32EF", later
versions beginning with the version 20190608-Base-Ratified removed this
restriction.  Because the 'E' extension is still a draft, the author chose
to *just* remove the conflict (not checking the ISA version).

Note that, because RV32E is only used with a soft-float calling convention,
there's no valid official ABI for RV32EF.  It means, even if we can assemble
a program with -march=rv32ef -mabi=ilp32e, floating-point registers are kept
in an unmanaged state (outside ABI management).

The purpose of this commit is to suppress unnecessary errors while parsing
an ISA string and/or disassembling, not to allow hard-float with RVE.

bfd/ChangeLog:

* elfxx-riscv.c (riscv_parse_check_conflicts): Accept RV32EF
because only older specifications disallowed it.

gas/ChangeLog:

* testsuite/gas/riscv/march-fail-rv32ef.d: Remove as not directly
prohibited.
* testsuite/gas/riscv/march-fail-rv32ef.l: Likewise.
bfd/elfxx-riscv.c
gas/testsuite/gas/riscv/march-fail-rv32ef.d [deleted file]
gas/testsuite/gas/riscv/march-fail-rv32ef.l [deleted file]