Tracking Issue for CRC32 intrinsics on 32-bit ARM
Open
Nobody has claimed this yet.
C-tracking-issue
O-Arm
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(stdarch_arm_crc32)]
This is a tracking issue for CRC32 intrinsics on ARM
Unstabilized ARM for intrinsics from previous issue https://github.com/rust-lang/rust/issues/117215#issue-1963289418
Public API
// core::arch::arm
pub unsafe fn __crc32b(crc: u32, data: u8) -> u32;
pub unsafe fn __crc32cb(crc: u32, data: u8) -> u32;
pub unsafe fn __crc32h(crc: u32, data: u16) -> u32;
pub unsafe fn __crc32ch(crc: u32, data: u16) -> u32;
pub unsafe fn __crc32w(crc: u32, data: u32) -> u32;
pub unsafe fn __crc32cw(crc: u32, data: u32) -> u32;
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 stdarch_arm_crc32 feature gate and the listed core::arch::arm public API. Review the linked previous issue and the implementation, FCP, and stabilization steps; the work is done only when the intrinsics progress through implementation and stabilization.
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
- Mostly clear
- Newbie friendliness
- 25/100