-
Notifications
You must be signed in to change notification settings - Fork 275
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
Tests: wrong instruction assertions #1209
Comments
This is somewhat intentional. It turns out that x86 has several instructions which all do the same thing (masked |
on x86_64-pc-windows-msvc using $Env:TARGET="x86_64-pc-windows-msvc"
$Env:RUSTFLAGS="-Ctarget-feature=+avx2"
cargo test --release the following tests fail with a wrong instruction assertion: List of tests
Using List of tests
Almost all of the ones follow a format something like:
For the first set, LLVM is clearly exploiting the fact that a given set of instructions was enabled for the compilation and is emitting the VEX prefixed version of instructions. The assertions weren't prepared for it and I think it broke something else, but honestly, I want to pat it on its head and say "good dragon!" I am less confident about what to make of the other set. Without optimizations or features on, most everything passes except for this, and I don't know if this is related:
|
Many intrinsics have wrong instruction assertions, e.g. all the AVX512
mm512_mask_blend_epi16*
check forvmovdqu16
instead ofvpblend*
, on aarch64vget_high_p64
tests forldr
instead ofext
, etc.Not sure how to systematically find the ones which are broken, but I can submit fixes for the ones I find.
The text was updated successfully, but these errors were encountered: