Has anyone run coremark.wasm with wasmtime's CLI? It always hangs for me.
wasm3's build of coremark.wasm (clicky) hangs forever when I run it in wasmtime. Other tools, like wasm3, wamrc, wasmer, etc run it fine. But wasmtime coremark.wasm
will happily run forever (I killed it after a day) at 100% CPU usage. I'm running on an M1 Max MacBook Pro.
I recall this coming up awhile back on https://github.com/bytecodealliance/wasmtime/issues/2737, and I think the conclusion at the time was that the wasm module itself is buggy
Thank you! I was struggling to find an existing issue but that's exactly what I was looking for.
Last updated: Nov 22 2024 at 17:03 UTC