←back to thread

Optimizing the Ion compiler back end

(spidermonkey.dev)
164 points undercut | 1 comments | 16 Oct 24 17:15 UTC | HN request time: 0.427s | source
Show context
zyedidia ◴[16 Oct 24 18:33 UTC] No.41862222[source]▶
Is there any AOT WebAssembly compiler that can compile Wasm used by websites? I tried locally compiling the Photoshop Wasm module mentioned in the article but the compilers I tried (Wasmtime, wasm2c, WAMR) all complained about some unsupported Wasm extension/proposal being required (exceptions seems like the blocker on wasmtime, and the others gave cryptic error messages).

Is it really the case that browsers have default-enabled all sorts of extensions that are not yet widely supported by the rest of the ecosystem?

replies(4): >>41862827 #>>41862830 #>>41863118 #>>41863297 #
1. aseipp ◴[16 Oct 24 19:50 UTC] No.41863118[source]▶
No, I think most of the AOT compilers in practice are a bit behind V8 and/or Spidermonkey for newer features. Realistically, most development driving new WASM features is motivated by website-ish use cases. Exception handling in particular is still not standardized so I guess it's expected that the browser engines would be the one to have the most evolving support (and the ability to test it thoroughly) because people want that platform as their inevitable target anyway.