-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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 failure when casting a SIMD type with -O3 #10425
Comments
It's worth noting that it also requires |
Will investigate! Thanks for the report :) |
So it looks like this is a bug in the SLP vectorizer pass. I have no idea how that pass works and it is not WebAssembly-specific, so it would be great if you could file an LLVM bug about this. |
Also, whoever wants to fix this bug probably doesn't have emscripten installed, so it would be helpful if you uploaded the automatically generated test file and script when you file that bug report. |
Thanks for looking into this! Reported to LLVM as https://bugs.llvm.org/show_bug.cgi?id=44954 |
@tlively, looks like a fix was merged. I'm not too familiar with how Emscripten tracks LLVM; when do you think the fix would get downstreamed into Emscripten? |
It should already be available via |
I'm not seeing it fixed when I do |
@abrown, as mentioned in the LLVM issue, this looks like a different bug. Can you cc me on any new issue you file? |
@tlively, in case I didn't do things the right way in BugZilla, here's a link to the new issue: https://bugs.llvm.org/show_bug.cgi?id=45178. |
This has been fixed. |
In attempting to build a Wasm SIMD version of libaom using SIMDe, I ran into the following crash when I add the
-O3
flag (it does not crash without this):This failure comes using the following
emcc -v
:The code being compiled is here and @nemequ reduced that file to a smaller test case:
I'm not exactly sure what is going on here so feel free to update the title or re-route this to LLVM if it is a bug there; I felt it was best to triage in Emscripten first to see what you all think.
The text was updated successfully, but these errors were encountered: