alexcrichton opened issue #12790:
This test case fails with:
$ cargo run -q test ../out.clif thread 'worker #3' (1866366) panicked at cranelift/codegen/src/opts.rs:191:5: unimplemented for > 64 bits note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [2026-03-16T22:42:10Z ERROR cranelift_filetests::concurrent] FAIL: panicked in worker #3: unimplemented for > 64 bits FAIL ../out.clif: panicked in worker #3: unimplemented for > 64 bits 1 tests Error: 1 failureoss-fuzz reports the regression range as https://github.com/bytecodealliance/wasmtime/compare/039ae2af85ed73090ba56741b6f8afb29cf04aa7...1b59b579856569d1a6ddca82429bf94f6fbef5e3 of which my guess is either https://github.com/bytecodealliance/wasmtime/pull/12738 or https://github.com/bytecodealliance/wasmtime/pull/12743 (cc @myunbin)
alexcrichton added the fuzz-bug label to Issue #12790.
alexcrichton closed issue #12790:
This test case fails with:
$ cargo run -q test ../out.clif thread 'worker #3' (1866366) panicked at cranelift/codegen/src/opts.rs:191:5: unimplemented for > 64 bits note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [2026-03-16T22:42:10Z ERROR cranelift_filetests::concurrent] FAIL: panicked in worker #3: unimplemented for > 64 bits FAIL ../out.clif: panicked in worker #3: unimplemented for > 64 bits 1 tests Error: 1 failureoss-fuzz reports the regression range as https://github.com/bytecodealliance/wasmtime/compare/039ae2af85ed73090ba56741b6f8afb29cf04aa7...1b59b579856569d1a6ddca82429bf94f6fbef5e3 of which my guess is either https://github.com/bytecodealliance/wasmtime/pull/12738 or https://github.com/bytecodealliance/wasmtime/pull/12743 (cc @myunbin)
Last updated: Mar 23 2026 at 16:19 UTC