Skip to content

Tracking Issue for CRC32 intrinsics on 32-bit ARM #125085

Open
@ssukanmi

Description

@ssukanmi

Feature gate: #![feature(stdarch_arm_crc32)]

This is a tracking issue for CRC32 intrinsics on ARM
Unstabilized ARM for intrinsics from previous issue #117215 (comment)

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.

Footnotes

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCO-ArmTarget: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 stateT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions