Skip to content

Fix Neon f16 stability #1818

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

Merged
merged 2 commits into from
Jun 2, 2025
Merged

Conversation

adamgemmell
Copy link
Contributor

In https://rust-lang.zulipchat.com/#narrow/channel/219381-t-libs/topic/is.20.60arch.3A.3Aaarch64.3A.3Afloat16x8_t.60.20supposed.20to.20be.20stable.3F/with/520762685 it was noted that some f16 Neon types were incorrectly stable when introduced and that some f16 Neon intrinsics were incorrectly changed from unstable to stable recently.

The latter is a regression from stable to beta and could be nominated for a beta backport, but I couldn't find any process or precedent for doing this on stdarch.

@rustbot
Copy link
Collaborator

rustbot commented Jun 2, 2025

r? @Amanieu

rustbot has assigned @Amanieu.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@Amanieu
Copy link
Member

Amanieu commented Jun 2, 2025

As much as this is correct, it's still going to be a pain to backport...

@Amanieu Amanieu added this pull request to the merge queue Jun 2, 2025
Merged via the queue into rust-lang:master with commit 5a27ac6 Jun 2, 2025
62 checks passed
@Amanieu
Copy link
Member

Amanieu commented Jun 2, 2025

If the FCP on rust-lang/rust#136306 passes then we could avoid backporting entirely.

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

Successfully merging this pull request may close these issues.

3 participants