Eric Astor
Eric Astor
For the record, I wasn't suggesting an `unsafe` block construct; I was suggesting an `unsafe proc`, the same way Rust has `unsafe fn`. But I see your point if we...
Per @hzeller: > bzlmod migration is mostly done, there are only a few outliers that still use WORKSPACE > > https://github.com/google/xls/blob/main/dependency_support/load_external.bzl shows the remaining things that need transfer. > >...
@richmckeever Any chance you'll be able to take a look soon?
I've just run into this as well. This would be a nice feature!
Can you confirm that `bazel run //xls/tools:eval_ir_main -- --test_llvm_jit --input='bits[57]:0x10; bits[24]:0xc6_c3c1; bits[50]:0x2_0000_0000' --llvm_opt_level=2 /tmp/crasher.ir` fails? What about `bazel run //xls/tools:eval_ir_main -- --test_llvm_jit --input='bits[57]:0x10; bits[24]:0xc6_c3c1; bits[50]:0x2_0000_0000' --llvm_opt_level=0 /tmp/crasher.ir` ?