afonso@DESKTOP-1AHKMV2:~/git/wasmtime/cranelift$ cargo run -- test ./lmao.clif
Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Running `/home/afonso/git/wasmtime/target/debug/clif-util test ./lmao.clif`
thread 'worker #0' panicked at cranelift/codegen/src/ir/instructions.rs:788:21:
The Narrower constraint only operates on floats or ints
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
ERROR cranelift_filetests::concurrent > FAIL: panicked in worker #0: The Narrower constraint only operates on floats or ints
FAIL ./lmao.clif: panicked in worker #0: The Narrower constraint only operates on floats or ints
1 tests
Error: 1 failure
Versions and Environment
Cranelift version or commit: main (62ad1185bcbf39a2668708c379f850e57e7ce780)
Operating system: Linux
Architecture: x86/64
Extra Info
Bisecting this gives the first bad commit as e39c6b76f9f01b5a5383a62a2a4a12997416cbef (cc: @fitzgen), but I think that just changed the heuristics of how we apply optimizations and It feels like it might be a preexisting issue that is only surfaced by that commit.
đ Hey,
I found this today when running the
cranelift-fuzzgen
fuzzer. This program compiles withopt_level=none
but fails withopt_level=speed
..clif
Test CaseSteps to Reproduce
clif-util test ./the-above.clif
Expected Results
The test to pass.
Actual Results
Versions and Environment
Cranelift version or commit: main (62ad1185bcbf39a2668708c379f850e57e7ce780)
Operating system: Linux
Architecture: x86/64
Extra Info
Bisecting this gives the first bad commit as e39c6b76f9f01b5a5383a62a2a4a12997416cbef (cc: @fitzgen), but I think that just changed the heuristics of how we apply optimizations and It feels like it might be a preexisting issue that is only surfaced by that commit.