Tracking Issue for AArch64 MTE memory tagging intrinsics
Open
Nobody has claimed this yet.
C-tracking-issue
F-stdarch_aarch64_mte
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_aarch64_mte)]
This is a tracking issue for AArch64 MTE memory tagging intrinsics.
Public API
// core::arch::aarch64
pub unsafe fn __arm_mte_create_random_tag<T>(src: *const T, mask: u64) -> *const T;
pub unsafe fn __arm_mte_increment_tag<const OFFSET: i64, T>(src: *const T) -> *const T;
pub unsafe fn __arm_mte_exclude_tag<T>(src: *const T, excluded: u64) -> u64;
pub unsafe fn __arm_mte_set_tag<T>(tag_address: *const T);
pub unsafe fn __arm_mte_get_tag<T>(address: *const T) -> *const T;
pub unsafe fn __arm_mte_ptrdiff<T, U>(a: *const T, b: *const U) -> i64;
Steps / History
- Implementation: https://github.com/rust-lang/stdarch/pull/1627
- 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
Review the implementation linked in rust-lang/stdarch PR 1627 and the listed core::arch::aarch64 API under the stdarch_aarch64_mte feature gate. The tracking issue shows implementation complete but is still awaiting the final comment period and stabilization PR; unresolved questions must be addressed before those steps can finish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100