diff options
| author | Tsukasa OI <floss_rust@irq.a4lg.com> | 2025-04-17 01:08:57 +0000 |
|---|---|---|
| committer | Amanieu d'Antras <amanieu@gmail.com> | 2025-04-23 19:32:43 +0000 |
| commit | 7db430fb80b17e9b9a996b33413f59d4b870b1fe (patch) | |
| tree | ff1414edcc11ab25953fd7dcc4a8b92b03a5ecb3 /tests/codegen-llvm/patchable-function-entry/patchable-function-entry-both-flags.rs | |
| parent | e61df091c1a54588f0ea6a58a646f030ea0e5ef5 (diff) | |
| download | rust-7db430fb80b17e9b9a996b33413f59d4b870b1fe.tar.gz rust-7db430fb80b17e9b9a996b33413f59d4b870b1fe.zip | |
std_detect: RISC-V platform guide documentation
Since there's no architectural feature detection on RISC-V (unlike `CPUID` on x86 architectures and some system registers on Arm/AArch64), runtime feature detection entirely depends on the platform-specific facility. As a result, availability of each feature heavily depends on the platform and its version. To help users make a decision for feature checking on a RISC-V system, this commit adds a platform guide with minimum supported platform versions. Note: It intentionally omits the description of the reverse implication related to *extension groups* (such like implication of `B` *from* its members: `Zba`, `Zbb` and `Zbs` extensions) because it currently does not synchronize well with the `-Ctarget-feature` compiler option (due to missing reverse implication checks using `cfg` and due to constraints of the current Rust's feature handling). Instead, it only describes forward implications (like `D` implying `F`) due to the fact that it relatively synchronizes well between Rust and `stdarch` for this kind of feature handling (not fully synchronized though). Still, an extension group is considered "supported" once the platform/version supports runtime detection of all members in it.
Diffstat (limited to 'tests/codegen-llvm/patchable-function-entry/patchable-function-entry-both-flags.rs')
0 files changed, 0 insertions, 0 deletions
