-
Notifications
You must be signed in to change notification settings - Fork 300
(Partially) Stabilize stdarch_neon_f16
#1922
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
base: master
Are you sure you want to change the base?
Conversation
|
Is there any reason not to stabilize The fcma intrinsics that don't depend on immediate |
Also one more thing, ideally don't update the feature name of the non-stabilized intrinsics, instead change the feature name of the stabilized ones. Otherwise it introduces compile errors in user code, for no good reason |
91ffa69
to
8cb1918
Compare
No. It's included in this pull request now.
Done.
Intrinsics are stablized under the new feature gate |
480dc48
to
24df9ae
Compare
24df9ae
to
fd621c6
Compare
Tracking issue: rust-lang/rust#136306 (waiting for FCP and rust-lang/rust#146613 probably)
stdarch_neon_fp16
.stdarch_neon_f16
types are still unstable on arm. They're gated bystdarch_arm_neon_intrinsics
now.stdarch_neon_f16
intrinsics are still unstable on arm. They're gated bystdarch_arm_neon_intrinsics
now.stdarch_neon_f16
intrinsics that requiresfhm
are stable.stdarch_neon_f16
intrinsics that requiresfcma
are still unstable. They're gated bystdarch_neon_fcma
now.stdarch_neon_f16
intrinsics that requireslut
are still unstable. They're gated bystdarch_neon_feat_lut
before and after this pull request.stdarch_neon_f16
intrinsics that takes or returnsf16
,*const f16
or*mut f16
are still unstable.List of stablized intrinsics.
List of unstable intrinsics.