Tracking Issue for `stdarch_aarch64_rand`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_aarch64_rand)]
This is a tracking issue for the aarch64 random number generation intrinsics, documented at https://arm-software.github.io/acle/main/acle.html#random-number-generation-intrinsics.
Public API
#[target_feature(enable = "rand")]
pub unsafe fn __rndr(value: *mut u64) -> i32 { /* ... */ }
#[target_feature(enable = "rand")]
pub unsafe fn __rndrrs(value: *mut u64) -> i32 { /* ... */ }
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: https://github.com/rust-lang/stdarch/pull/2050
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- LLVM uses
randas the name of the target feature, while arm seems to be usingrnginternally.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the public API and the implementation in stdarch PR 2050. Review the unresolved question about LLVM’s rand target feature name versus Arm’s internal rng name, then check the remaining FCP and stabilization steps. Done means the lifecycle decisions are resolved and the appropriate tracking checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100