You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was discovered with our fuzzer as crasher_2024-09-14_6bbb.x, then minimized.
To Reproduce
Run eval_ir_main over the above IR, passing --input='bits[28]:0x1' --test_llvm_jit.
Expected behavior
Results should agree between the interpreter and the JIT.
Additional context
This appears to be an LLVM bug; the issue goes away if we turn off LLVM optimization. I've used //xls/dev_tools:dump_llvm_artifacts to create a self-contained demonstration of the issue, and filed it as llvm/llvm-project#108828
The text was updated successfully, but these errors were encountered:
Describe the bug
eval_ir_main
produces different results for the following IR with the interpreter and the JIT:This was discovered with our fuzzer as
crasher_2024-09-14_6bbb.x
, then minimized.To Reproduce
Run
eval_ir_main
over the above IR, passing--input='bits[28]:0x1' --test_llvm_jit
.Expected behavior
Results should agree between the interpreter and the JIT.
Additional context
This appears to be an LLVM bug; the issue goes away if we turn off LLVM optimization. I've used
//xls/dev_tools:dump_llvm_artifacts
to create a self-contained demonstration of the issue, and filed it as llvm/llvm-project#108828The text was updated successfully, but these errors were encountered: