Tracking Issue for AArch64 prefetch intrinsic
Open
Nobody has claimed this yet.
C-tracking-issue
O-AArch64
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_aarch64_prefetch)]
This is a tracking issue for the AArch64 _prefetch intrinsic.
Public API
// core::arch::aarch64
pub const _PREFETCH_READ: i32;
pub const _PREFETCH_WRITE: i32;
pub const _PREFETCH_LOCALITY0: i32;
pub const _PREFETCH_LOCALITY1: i32;
pub const _PREFETCH_LOCALITY2: i32;
pub const _PREFETCH_LOCALITY3: i32;
pub unsafe fn _prefetch<const RW: i32, const LOCALITY: i32>(p: *const i8);
Steps / History
- Implementation: #...
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
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 core::arch::aarch64 public API and the stdarch_aarch64_prefetch feature gate described in this issue. Check the linked implementation work when it exists; the issue currently lists no implementation PR. Done requires completing the implementation, final comment period, and stabilization PR tracked in the issue.
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
- 30/100