You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original WASM paper used PolyBenchC as a benchmark suite. It would be interesting to get this working with cmm_of_wasm, so we can get some performance measurements against:
The interpreter
wasm2c
The V8 JIT
The SpiderMonkey JIT
My guess is we're not going to match the production-quality JITs, and that we will easily obliterate the performance of the interpreter. But wasm2c is the interesting one, as it's the only other pipeline to getting natively-compiled WASM.
The text was updated successfully, but these errors were encountered:
The original WASM paper used PolyBenchC as a benchmark suite. It would be interesting to get this working with
cmm_of_wasm
, so we can get some performance measurements against:wasm2c
My guess is we're not going to match the production-quality JITs, and that we will easily obliterate the performance of the interpreter. But
wasm2c
is the interesting one, as it's the only other pipeline to getting natively-compiled WASM.The text was updated successfully, but these errors were encountered: