Skip to content

mark vstl1_* functions as unsafe#2092

Draft
folkertdev wants to merge 1 commit intorust-lang:mainfrom
folkertdev:rcpc3-pub-unsafe
Draft

mark vstl1_* functions as unsafe#2092
folkertdev wants to merge 1 commit intorust-lang:mainfrom
folkertdev:rcpc3-pub-unsafe

Conversation

@folkertdev
Copy link
Copy Markdown
Contributor

@folkertdev folkertdev commented Apr 24, 2026

fixes rust-lang/rust#155751

these functions write to a raw pointer, and so are clearly unsafe to use

these functions write to a raw pointer, and so are clearly unsafe to use
static_defs: ["const LANE: i32"]
safety: safe
safety:
unsafe: [neon]
Copy link
Copy Markdown
Contributor Author

@folkertdev folkertdev Apr 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adamgemmell using neon here is not right, this is unsafe in its own right. I'm not sure if there are further safety conditions though, the link to the documentation that is generated for these functions does not work.

I also haven't quite reverse-engineered the right yaml to use to get a better message here.

View changes since the review

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.

Safe Neon store-release intrinsics marked safe but should be unsafe

1 participant