Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tracking Issue for stdarch_arm_feature_detection #111190

Open
2 tasks
Amanieu opened this issue May 4, 2023 · 1 comment
Open
2 tasks

Tracking Issue for stdarch_arm_feature_detection #111190

Amanieu opened this issue May 4, 2023 · 1 comment
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@Amanieu
Copy link
Member

Amanieu commented May 4, 2023

Feature gate: #![feature(stdarch_arm_feature_detection)]

This is a tracking issue for ARM target feature detection.

Public API

// std::arch

macro_rules! is_arm_feature_detected { .. }

Steps / History

  • Final comment period (FCP)1
  • Stabilization PR

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
@Amanieu Amanieu added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. labels May 4, 2023
@Jules-Bertholet
Copy link
Contributor

@rustbot label O-arm

@rustbot rustbot added the O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state label May 5, 2023
kkysen added a commit to memorysafety/rav1d that referenced this issue Sep 23, 2023
@kkysen
fn dav1d_get_cpu_flags_arm: Use `is_{arm,aarch64}_feature_detected!…
aa5be48 
…` for CPU feature detection.

`is_arm_feature_detected!` is still unstable (rust-lang/rust#111190),
so we have to enable `#![feature(stdsimd)]` on `arm`,
though it doesn't look like this part of `stdsimd` is likely to change.
kkysen added a commit to memorysafety/rav1d that referenced this issue Sep 23, 2023
@kkysen
fn dav1d_get_cpu_flags_arm: Use `is_{arm,aarch64}_feature_detected!…
ec8ec92 
…` for CPU feature detection.

`is_arm_feature_detected!` is still unstable (rust-lang/rust#111190),
so we have to enable `#![feature(stdsimd)]` on `arm`,
though it doesn't look like this part of `stdsimd` is likely to change.
kkysen added a commit to memorysafety/rav1d that referenced this issue Sep 25, 2023
@kkysen
fn dav1d_get_cpu_flags_arm: Use `is_{arm,aarch64}_feature_detected!…
8fdc218 
…` for CPU feature detection.

`is_arm_feature_detected!` is still unstable (rust-lang/rust#111190),
so we have to enable `#![feature(stdsimd)]` on `arm`,
though it doesn't look like this part of `stdsimd` is likely to change.
@Amanieu Amanieu mentioned this issue Oct 26, 2023
Merged
@zachs18 zachs18 mentioned this issue Feb 8, 2024
Closed
@Amanieu Amanieu mentioned this issue Mar 10, 2024
Closed
3 tasks
@kkysen kkysen mentioned this issue May 23, 2024
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. O-Arm Target: 32-bit Arm processors (armv6, armv7, thumb...), including 64-bit Arm in AArch32 state T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Amanieu @rustbot @Jules-Bertholet