-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
LLVM assertion in simdnoise crate #56483
Comments
Wow, this one's amazing. |
This one still reproduces on master. |
Unfortunately, I wasn't able to get this to assert with |
Can an absolute beginner take this one?Let me know if someone is working on this already |
@FrankSD This is an assertion failure in the very depths of LLVM's machine code backend, you can try to find a minimal test case if you want, but I wouldn't recommend finding or fixing the actual bug to a beginner (but feel free to try if you feel very ambitious!). You can also try your hand at one of the E-Easy issues, which are specifically meant for beginners. |
|
@mati865 Did you use an assertion-enabled build? I tried again just now and am still seeing the assertion:
|
@nikic my bad, new nightly builds don't have llvm assertions enabled. |
Update stdarch submodule Changes included: * Use a bootstrap guard for modules with new target features * Avoid calling intrinsics with invalid const arguments * Avx512bw * Avx512cd * Add AVX512BITALG * Add GFNI Intrinsics * Add AVX512VPOPCNTDQ Intrinsics * Add VPCLMULQDQ Intrinsics * Avx512bw * Reimplement `_xgetbv` with LLVM intrinsics * Avx512bw * Add reamained vmax and vmin via auto-generated code * Add VAES intrinsics Fixes rust-lang#56483.
The simdnoise crate is failing to build with an LLVM assertion:
This is not a regression, it's confirmed to also fail on 1.28.0 (alt builds are not available past that).
The text was updated successfully, but these errors were encountered: