diff options
author | Alex Bradbury <asb@igalia.com> | 2024-10-28 07:42:33 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-10-28 07:42:33 +0000 |
commit | 35f6cc6af09f48f9038fce632815a2ad6ffe8689 (patch) | |
tree | c15dc52da5d9daf0e962481dc55225e0b962e748 /llvm/lib/CodeGen/MachineOperand.cpp | |
parent | e7f422d5c2ea05704eaab2cdd67a8b1ebc55e95b (diff) | |
download | llvm-35f6cc6af09f48f9038fce632815a2ad6ffe8689.zip llvm-35f6cc6af09f48f9038fce632815a2ad6ffe8689.tar.gz llvm-35f6cc6af09f48f9038fce632815a2ad6ffe8689.tar.bz2 |
[RISCV] Add the Sha extension (#113820)
This was introduced in the now-ratified RVA23 profile (and also added to
the RVA22 text) as a simple way of referring to H plus the set of
supervisor extensions required by RVA23.
https://github.com/riscv/riscv-profiles/blob/main/src/rva23-profile.adoc
This patch simply defines the extension. The next patch will adjust the
RVA23 profile to use it, and at that point I think we will be ready to
mark RVA23 as non-experimental.
Note that I haven't made it so if you enable all extensions that
constitute Sha, Sha is implied. Per #76893 (adding 'B'), the concern is
making this implication might break older external assemblers. Perhaps
this is less of a concern given the relative frequency of
`-march=${foo}_zba_zbb_zbs` vs the collection of H extensions. If we did
want to add that implication, we'd probably want to add it in a separate
patch so it can be easily reverted if found to cause problems.
Diffstat (limited to 'llvm/lib/CodeGen/MachineOperand.cpp')
0 files changed, 0 insertions, 0 deletions