WASM 3.0 Completed
webassembly.org
WASM 3.0 Completed
1–10 of 520 posts
Re: WASM 3.0 Completed
#2Has anyone benchmarked 64bit memory on the current implementations? There's the potential for performance regressions there because they could exploit the larger address space of 64bit hosts to completely elide bounds checks when running 32bit WASM code, but that doesn't work if the WASM address space is also 64bit.
Re: WASM 3.0 Completed
#3This looks like a great release! Lots of stuff people have wanted for a long time in here.
Re: WASM 3.0 Completed
#4> Garbage collection. In addition to expanding the capabilities of raw linear memories, Wasm also adds support for a new (and separate) form of storage that is automatically managed by the Wasm runtime via a garbage collector. Staying true to the spirit of Wasm as a low-level language, Wasm GC is low-level as well: a compiler targeting Wasm can declare the memory layout of its runtime data structures in terms of struct and array types, plus unboxed tagged integers, whose allocation and lifetime is then handled by Wasm. But that’s it.
Wow!
Re: WASM 3.0 Completed
#5Has anyone benchmarked 64bit memory on the current implementations? There's the potential for performance regressions there because they could exploit the larger address space of 64bit hosts to completely elide bounds checks when running 32bit WASM code, but that doesn't work if the WASM address space is also 64bit.
> WebAssembly apps tend to run slower in 64-bit mode than they do in 32-bit mode. This performance penalty depends on the workload, but it can range from just 10% to over 100%—a 2x slowdown just from changing your pointer size.
> This is not simply due to a lack of optimization. Instead, the performance of Memory64 is restricted by hardware, operating systems, and the design of WebAssembly itself.
https://spidermonkey.dev/blog/2025/01/15/is-memory64-actuall...
Re: WASM 3.0 Completed
#6> GC and Exception handling
This was not necessary.. what a mistake, specially EH..
Re: WASM 3.0 Completed
#7This looks like a great release! Lots of stuff people have wanted for a long time in here.
Tail calls. Tail calls!
Re: WASM 3.0 Completed
#8> GC and Exception handling This was not necessary.. what a mistake, specially EH..
Not including GC would have been a mistake. Having to carry a complete garbage collector with every program, especially on platforms like browsers were excellent ones already exist, would have been a waste.
Re: WASM 3.0 Completed
#9Does anyone know whether the exception handling implementation supports restartable exceptions like Common Lisp's and Scheme's?
Re: WASM 3.0 Completed
#10> GC and Exception handling This was not necessary.. what a mistake, specially EH..
WASM isn't a language, so them adding stuff like this serves to increase performance and standardize rather than forcing compilers to emulate common functionality.