-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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.
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
Tracking Issue for NEON intrinsics on 32-bit ARM #111800
Comments
In #126555 all SIMD types have been changed to require |
So what happens when I use the type and don't have NEON enabled? |
Note that this feature is currently unsound due to #129880. |
I appear to have missed a few words: the PR changes it so that NEON is required to use the SIMD types as inputs or outputs of inline assembly. Non-inline-assembly uses are unaffected. I've updated the original comment. |
Ah, makes sense. :) Once #127731 lands, we should probably also require NEON when passing vectors to/from non-Rust-ABI functions. |
Another unsoundness due to codegen: rust-lang/stdarch#1217 |
Currently only runs on `aarch64`, because `arm` NEON intrinsics are unstable: rust-lang/rust#111800
Feature gate:
#![feature(stdarch_arm_neon_intrinsics)]
This is a tracking issue for the NEON intrinsics in
core::arch::arm
. This was split off from #90972 which tracked the AArch64 NEON intrinsics which have now been stabilized.Public API
Everything in
core::arch::arm
that starts with the letterv
.Steps / History
Unresolved Questions
Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: