alexcrichton opened issue #4857:
On
main
:$ cargo run compile foo.wat Finished dev [unoptimized + debuginfo] target(s) in 0.13s Running `target/debug/wasmtime compile foo.wat` thread '<unnamed>' panicked at 'explicit panic', cranelift/codegen/src/scoped_hash_map.rs:125:30 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
with this input:
(module (func i32.const 0 if ;; label = @0 unreachable end f32.const nan drop ) )
I believe this was introduced in https://github.com/bytecodealliance/wasmtime/pull/4849 (cc @afonso360 and @jameysharp )
alexcrichton labeled issue #4857:
On
main
:$ cargo run compile foo.wat Finished dev [unoptimized + debuginfo] target(s) in 0.13s Running `target/debug/wasmtime compile foo.wat` thread '<unnamed>' panicked at 'explicit panic', cranelift/codegen/src/scoped_hash_map.rs:125:30 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
with this input:
(module (func i32.const 0 if ;; label = @0 unreachable end f32.const nan drop ) )
I believe this was introduced in https://github.com/bytecodealliance/wasmtime/pull/4849 (cc @afonso360 and @jameysharp )
jameysharp commented on issue #4857:
You're right. Given a little finesse, I think I can revert the changes to
Ieee32
andIeee64
without undoing the rest of the work.
jameysharp closed issue #4857:
On
main
:$ cargo run compile foo.wat Finished dev [unoptimized + debuginfo] target(s) in 0.13s Running `target/debug/wasmtime compile foo.wat` thread '<unnamed>' panicked at 'explicit panic', cranelift/codegen/src/scoped_hash_map.rs:125:30 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
with this input:
(module (func i32.const 0 if ;; label = @0 unreachable end f32.const nan drop ) )
I believe this was introduced in https://github.com/bytecodealliance/wasmtime/pull/4849 (cc @afonso360 and @jameysharp )
Last updated: Dec 23 2024 at 13:07 UTC