[llvm] [RISCV][doc] Add note to RISCVUsage about supported atomics ABIs (PR #103879)

Alex Bradbury via llvm-commits llvm-commits at lists.llvm.org
Thu Aug 15 06:19:46 PDT 2024


================
@@ -280,6 +280,11 @@ Supported
 ``Za128rs``, ``Za64rs``, ``Zama16b``, ``Zic64b``, ``Ziccamoa``, ``Ziccif``, ``Zicclsm``, ``Ziccrse``, ``Shcounterenvw``, ``Shgatpa``, ``Shtvala``, ``Shvsatpa``, ``Shvstvala``, ``Shvstvecd``, ``Ssccptr``, ``Sscounterenw``, ``Ssstateen``, ``Ssstrict``, ``Sstvala``, ``Sstvecd``, ``Ssu64xl``, ``Svade``, ``Svbare``
   These extensions are defined as part of the `RISC-V Profiles specification <https://github.com/riscv/riscv-profiles/releases/tag/v1.0>`__.  They do not introduce any new features themselves, but instead describe existing hardware features.
 
+Atomics ABIs
+============
+
+At the time of writing there are three atomics mappings (ABIs) `defined for RISC-V <https://github.com/riscv-non-isa/riscv-elf-psabi-doc/blob/master/riscv-elf.adoc#tag_riscv_atomic_abi-14-uleb128version>__`.  As of LLVM 19, LLVM defaults to "A6S", which is compatible with both the original "A6" and the future "A7" ABI. See `the psABI atomics document <https://github.com/riscv-non-isa/riscv-elf-psabi-doc/blob/master/riscv-atomic.adoc>`__ for more information on these mappings.
----------------
asb wrote:

You're right there's an argument for linking to a specific version. My thinking is that the risk of confusion due to pointing someone to an older description that has since been extended/improved is probably greater than the risk of the link becoming dead. But I don't feel strongly, so if someone feels strongly we should link to a specific commit I'd be happy to change.

https://github.com/llvm/llvm-project/pull/103879


More information about the llvm-commits mailing list