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.

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

std docs list all NEON intrinsics as unstable #95086

Closed
tmandry opened this issue Mar 18, 2022 · 2 comments
Closed

std docs list all NEON intrinsics as unstable #95086

tmandry opened this issue Mar 18, 2022 · 2 comments

Comments

@tmandry
Copy link
Member

tmandry commented Mar 18, 2022

std docs are assumed to be the source of truth but claim that all neon intrinsics (including the recently stabilized ones on arm64) are still unstable, which is very confusing*.

From #90972 (comment) and #90972 (comment):

The intrinsics that are shared with the 32-bit ARM targets are basically partially stable; stable on AArch64, unstable on 32-bit. Rustdoc doesn't seem to be able to handle that.

Screen Shot 2022-03-18 at 12 09 09 PM

Even though these intrinsics are exposed behind a aarch64 module, they are internally shared with other arm platforms, hence the need to have target-dependent stability attributes on them.

(*) Source: I know multiple people who were confused, myself included!

cc #90972

@ehuss
Copy link
Contributor

ehuss commented Mar 18, 2022

This is tracked on the stdarch side as rust-lang/stdarch#1268, which has some more detail on the situation.

@Dylan-DPC
Copy link
Member

Closing this as it is tracked by the issue linked above.

@Dylan-DPC Dylan-DPC closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants