These are the changes I was looking for, thanks :)
 

> WebAssembly
>    
>    - We landed <https://bugzilla.mozilla.org/show_bug.cgi?id=1728897>
>     more changes <https://groups.google.com/g/19216811> for Wasm exception 
>    <https://groups.google.com/g/192168ll> support.
>    - Executable code for Wasm modules can now be cached 
>    <https://groups.google.com/g/login-page> in the network cache. We also 
>    added <https://groups.google.com/g/localhosts> gzip compression for 
>    this.
>    - The fuzzing team integrated 
>    <https://bugzilla.mozilla.org/show_bug.cgi?id=1720866> the wasm-smith 
>    
> <https://github.com/bytecodealliance/wasm-tools/tree/main/crates/wasm-smith> 
> fuzzer 
>    in SpiderMonkey.
>    - We prototyped <https://groups.google.com/g/convert-live> various 
>    instructions that are part of the Relaxed SIMD proposal 
>    
> <https://github.com/WebAssembly/relaxed-simd/blob/main/proposals/relaxed-simd/Overview.md>
>    .
>    - Code allocation failures are now reported 
>    <https://bugzilla.mozilla.org/show_bug.cgi?id=1337723> to the console.
>    - We fixed <https://bugzilla.mozilla.org/show_bug.cgi?id=1728781> a 
>    performance cliff in the register allocator that caused hangs on certain 
>    large Wasm modules.
>    - We landed <https://bugzilla.mozilla.org/show_bug.cgi?id=1727084> the 
>    remaining functionality for Wasm64 
>    
> <https://github.com/WebAssembly/memory64/blob/main/proposals/memory64/Overview.md>
>    .
>    - Type definitions for Wasm GC support are now properly collected 
>    <https://bugzilla.mozilla.org/show_bug.cgi?id=1731121>.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/aec473e1-d904-4cc9-8c0c-2b0ac6acf35cn%40mozilla.org.

Reply via email to