Sourced from wasmi's releases.
v0.31.1 - 2023-12-01
Fixes
- Fixed a bug, in the
wasmiengine executor, that causes an out of bounds buffer write when calling or resuming a Wasm function with a high number of parameters from the host side.
Sourced from wasmi's changelog.
Changelog
All notable changes to this project will be documented in this file.
The format is loosely based on Keep a Changelog, and this project adheres to Semantic Versioning. Additionally we have an
Internalsection for changes that are of interest to developers.Dates in this file are formattes as
YYYY-MM-DD.[
0.32.0-beta.5] - 2024-01-15Note:
- This is the beta of the upcoming
v0.32.0release. This version is not production ready yet and might contain serious bugs. Please use this only for experimentation or at your own risk.- Performance tests indicated that the new register-machine bytecode based Wasmi engine performance is very sensitive to hardware or OS specifics which may lead to very different performance characteristics.
- We are working on fixing this until the stable release.
- Measurements concluded that execution performance can be equal or sometimes even surpass Wasm3 execution performance.
Added
- Added a new execution engine based on register-machine bytecode. (paritytech/wasmi#729)
- The register-machine Wasmi
Engineexecutes roughly 80-100% faster and compiles roughly 30% slower according to benchmarks conducted so far.- Added
Module::new_uncheckedAPI. (paritytech/wasmi#829)
- This allows to compile a Wasm module without Wasm validation which can be useful when users know that their inputs are valid Wasm binaries.
- This improves Wasm compilation performance for faster startup times by roughly 10-20%.
- Added Wasm compilation modes. (paritytech/wasmi#844)
- When using
Module::newWasmi eagerly compiles Wasm bytecode into Wasmi bytecode which is optimized for efficient execution. However, this compilation can become very costly especially for large Wasm binaries.- The solution to this problem is to introduce new compilation modes, namely:
CompilationMode::Eager: Eager compilation, what Wasmi did so far. (default)CompilationMode::LazyTranslation: Eager Wasm validation and lazy Wasm translation.CompilationMode::Lazy: Lazy Wasm validation and translation.- Benchmarks concluded that
CompilationMode::LazyTanslation: Usually improves startup performance by a factor of 2 to 3.CompilationMode::Lazy: Usually improves startup performance by a factor of up to 27.- Note that
CompilationMode::Lazycan lead to partially validated Wasm modules which can introduce non-determinism when using different Wasm implementations. Therefore users should know what they are doing when usingCompilationMode::Lazyif this is a concern.- Enable lazy Wasm compilation with:
let mut config = wasmi::Config::default();
... (truncated)
0218dfc
Fix InstanceCache bug (#904)3fd0cc2
Bump wasmi_arena version (#903)86c8740
Fix Sync impl bug in wasmi_arena crate (#902)27def28
Bump actions/cache from 3 to 4 (#900)59f9acc
Fix typos (#899)4c06acd
Update and improve Wasmi's readme (#898)2354a20
Prepare release for Wasmi v0.32.0 beta.5 (#893)a4dc251
Fix heap buffer overflow due to Wasmi codegen bug (#892)e60da49
Add CI test job using LLVM's Address Sanitizer (#891)28c770a
Prepare release for Wasmi v0.32.0-beta.4 (#889)