This changelog summarizes major changes to the WebAssembly engine implemented in GraalVM (GraalWasm).
- Changed the representation of WebAssembly control flow structures to a flat model. Loops and branches are now represented by jumps rather than separated AST nodes.
- Implemented the Sign-Extension-Ops proposal. It is available
behind the experimental option
--wasm.SignExtensionOps. - GraalWasm adopted the new Frame API.
- (GR-32924) Added support for importing and exporting mutable globals to GraalWasm, as defined by the respective WebAssembly proposal: https://github.com/WebAssembly/mutable-global/blob/master/proposals/mutable-global/Overview.md
- (GR-26941) Moved the module-validation checks to an earlier stage, so that the module is completely validated during
parsing, instead of being validated late, during linking and instantiation. All validation errors are now properly
reported when
Context#evalfrom the Polyglot API is invoked, and similarly when invokingWebAssembly.validatefrom the JS-WebAssembly Interface API. - (GR-33183) Memory-access performance was improved by avoiding a branch due to a out-of-bounds check.
- (GR-32714) Loop-profiling in GraalWasm was made more accurate to enable more loop optimizations.
- (GR-33227) Changed the Interop objects in GraalWasm to allow object-caching in the JS-WebAssembly Interface: https://webassembly.github.io/spec/js-api/index.html#object-caches
- (GR-32356) Fixed a bug that caused an overflow during memory or table initialization.
- (GR-33296) Added notifications to JavaScript when the memory grows (i.e., when
mem_growinstruction executes). This improves the compliance of the JS-WebAssembly Interface API. - (GR-33333) Added support for
BigInt-to-i64conversion in the JS-WebAssembly Interface API: https://github.com/WebAssembly/JS-BigInt-integration - (GR-32590) Improved internal implementation of GraalWasm to make JS-WebAssembly Interface API more compliant.