-
Notifications
You must be signed in to change notification settings - Fork 182
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
[fuzz] Crash in LLVM via eval_ir_main, target-independent node not lowered #1776
Labels
Comments
Odd configuring msan removes the error (though that does actually change the code the jit creates so its not impossible that would be expected). Running with asan points at LLVM X86DAGToDAGISel as the allocator of that node. This could be an llvm issue.
|
Yeah it seems to be an llvm bug in -O3 x64 codegen. I'll file a bug.
|
copybara-service bot
pushed a commit
that referenced
this issue
Dec 19, 2024
This can be useful if the llvm optimizer is crashing to aid in debugging. Bug: #1776 PiperOrigin-RevId: 707988660
allight
added
the
waiting-on-llvm
E.g. for fuzz bugs waiting for resolution of LLVM issues.
label
Dec 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
IR is here: sample.ir.txt
Testevector is here: testvector.pbtxt.txt
Expected behavior
No LLVM crash
Environment (this can be helpful for troubleshooting):
Additional context
Was fuzzing overnight after #1774
The text was updated successfully, but these errors were encountered: