intrinsic-test: add filters for sve#2169
Open
davidtwco wants to merge 6 commits into
Open
Conversation
Various SVE intrinsics are not yet implemented in stdarch, but are present in the `arm_intrinsics.json` and so should be skipped.
SVE intrinsics aren't available on big endian
The output of these cannot be compared.
`sveorv` intrinsics trigger a miscompile in LLVM where the call to the Rust intrinsic is optimised out and replaced with a zero, which is incorrect.
These tests require that we generate test arrays with values that are valid when cast to a pointer, which we don't currently support.
GCC quickly ICEs when asked to compile intrinsic-test's wrapper sources.
This was referenced Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out from #2160. This patch just adds filters to
ArmArchitectureTest::createto skip all of the SVE intrinsics that we won't want to test - either because of bugs in GCC or LLVM; because they are unimplemented; can't be tested; because we don't have the infrastructure for them yet.r? @sayantn