Tracking Issue for ARM CRC32 intrinsics

[Amanieu]

Feature gate: #![feature(stdarch_arm_crc32)]

This is a tracking issue CRC32 intrinsics on ARM and AArch64.

Public API

// core::arch::{arm,aarch64}

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;

// core::arch::aarch64

pub unsafe fn __crc32d(crc: u32, data: u64) -> u32;
pub unsafe fn __crc32cd(crc: u32, data: u64) -> u32;

Steps / History

• Implementation: #...
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[Jules-Bertholet]

@rustbot label o-aarch64 o-arm a-simd

[Amanieu]

These intrinsics are documented as part of the ARM C language extensions.

@rfcbot fcp merge

[rfcbot]

Team member @Amanieu has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.