aboutsummaryrefslogtreecommitdiff
path: root/gprofng/common/hwcdrv.c
diff options
context:
space:
mode:
authorTsukasa OI <research_trasio@irq.a4lg.com>2022-09-10 06:49:43 +0000
committerTsukasa OI <research_trasio@irq.a4lg.com>2022-09-30 04:02:13 +0000
commitd6b99a80716d2f0e21baae97a8653204dd354ad3 (patch)
tree2b929f2c661f19267768d8e1753062b0706156d8 /gprofng/common/hwcdrv.c
parentf3700471469ac0f395961e92892bc5d6e17ca177 (diff)
downloadbinutils-d6b99a80716d2f0e21baae97a8653204dd354ad3.zip
binutils-d6b99a80716d2f0e21baae97a8653204dd354ad3.tar.gz
binutils-d6b99a80716d2f0e21baae97a8653204dd354ad3.tar.bz2
RISC-V: Add privileged extensions without instructions/CSRs
Currently, GNU Binutils does not support following privileged extensions: - 'Smepmp' - 'Svnapot' - 'Svpbmt' as they do not provide new CSRs or new instructions ('Smepmp' extends the privileged architecture CSRs but does not define the CSR itself). However, adding them might be useful as we no longer have to "filter" ISA strings just for toolchains (if full ISA string is given by a vendor, we can straightly use it). And there's a fact that supports this theory: there's already an (unprivileged) extension which does not provide CSRs or instructions (but only an architectural guarantee): 'Zkt' (constant timing guarantee for certain subset of RISC-V instructions). This simple commit simply adds three privileged extensions listed above. bfd/ChangeLog: * elfxx-riscv.c (riscv_supported_std_s_ext): Add 'Smepmp', 'Svnapot' and 'Svpbmt' extensions.
Diffstat (limited to 'gprofng/common/hwcdrv.c')
0 files changed, 0 insertions, 0 deletions