Build your own WebAssembly Compiler (2019)

Re:Build your own WebAssembly Compiler (2019) by flohofwoe on Sunday December 03, 2023 @12:01PM (#38508544)

At least in Chrome, WASM is actually jitted and "tiered" on function level. Not sure how relevant this post still is, but AFAIK if anything changed then that the number of tiers has increased rather than decreased:

https://v8.dev/docs/wasm-compilation-pipeline

This may actually introduce visible "warmup-stutter" in rendering applications which is very unfortunate, but AFAIK the tiering was introduced to accommodate massive WASM blobs such as created by Unity which otherwise might take tens of seconds to AOT-compile.

[ Parent | on HN ]

Re:Build your own WebAssembly Compiler (2019) by tsegratis on Sunday December 03, 2023 @05:48PM (#38511571)

Maybe something like signed compilations is an answer -- a trusted source signs and verifies pre-compiled code

Then browsers can skip verification+jit etc if they trust the signature

[ Parent | on HN ]

Re:Build your own WebAssembly Compiler (2019) by AgentME on Sunday December 03, 2023 @06:11PM (#38511751)

You could use zero-knowledge proofs to prove that a given native binary was created from a specific compilation process and WASM binary. No privileged trusted authority necessary.

Though any pre-compiled binaries would be browser version specific and CPU architecture specific, so it might be too much of a pain for browsers and websites to bother with yet for small gains.

[ Parent | on HN ]