aboutsummaryrefslogtreecommitdiff
path: root/libiberty/getpwd.c
diff options
context:
space:
mode:
authorTsukasa OI <research_trasio@irq.a4lg.com>2023-08-12 00:38:18 +0000
committerTsukasa OI <research_trasio@irq.a4lg.com>2023-08-29 13:48:19 +0000
commitf30d6a48635b5b180e46c51138d0938d33abd942 (patch)
treece4210469026bbf88d5fb81b9dfd485ea86d4b7f /libiberty/getpwd.c
parentfea5442127daf8472966360279d402023dba3379 (diff)
downloadgcc-f30d6a48635b5b180e46c51138d0938d33abd942.zip
gcc-f30d6a48635b5b180e46c51138d0938d33abd942.tar.gz
gcc-f30d6a48635b5b180e46c51138d0938d33abd942.tar.bz2
RISC-V: Add stub support for existing extensions (unprivileged)
After commit c283c4774d1c ("RISC-V: Throw compilation error for unknown extensions") changed how do we handle unknown extensions, we have no guarantee that we can share the same architectural string with Binutils (specifically, the assembler). To avoid compilation errors on shared Assembler-C/C++ projects or programs with inline assembler, GCC should support almost all extensions that Binutils support, even if the GCC itself does not touch a thing. This commit adds stub supported standard unprivileged extensions to riscv_ext_version_table and its implications to riscv_implied_info (all information is copied from Binutils' bfd/elfxx-riscv.c except not yet merged 'Zce', 'Zcmp' and 'Zcmt' support). gcc/ChangeLog: * common/config/riscv/riscv-common.cc (riscv_implied_info): Add implications from unprivileged extensions. (riscv_ext_version_table): Add stub support for all unprivileged extensions supported by Binutils as well as 'Zce', 'Zcmp', 'Zcmt'. gcc/testsuite/ChangeLog: * gcc.target/riscv/predef-31.c: New test for a stub unprivileged extension 'Zcb' with some implications.
Diffstat (limited to 'libiberty/getpwd.c')
0 files changed, 0 insertions, 0 deletions