Robin Freyler
Robin Freyler
Closes https://github.com/wasmi-labs/wasmi/issues/922 This is going to be a larger effort and low-priority so I will be working on it from time to time. Inspired by: https://github.com/bytecodealliance/wasmtime/tree/main/crates/c-api/ # TODO - [x]...
Closes https://github.com/wasmi-labs/wasmi/issues/972. # TODO - [x] `trap` - [x] `fuel.consume` - [x] `return` instructions - [x] `return.nez` instructions - [x] `return.call` instructions - [x] `branch` instructions - [x] `branch.table` -...
Currently Wasmi support fuel metering of its internal Wasmi bytecode. The fuel is metered to the Wasmi bytecode that is resulting after the entire translation process with all the optimizations....
This is about adding a `Store::call_hook` API similar to Wasmtime's [`Store::call_hook`](https://docs.rs/wasmtime/22.0.0/wasmtime/struct.Store.html#method.call_hook) in order to improve Wasmi's Wasmtime API mirroring.} This should not regress performance of host function calls or the...
The `wasmi` crate became very large over the recent years with all the added functionality and the new register-machine engine. While compilation times are not yet an issue we might...
Currently there is no out-of-the-box way to profile Wasm executions via Wasmi. One way this could look like is to collect information during Wasm executions such as total number of...
Currently it is not easily possible to debug or pretty print Wasmi bytecode as generated by the `wasmi::Engine`. However, for debugging or inspection purposes or simply for learning how Wasmi...
Closes https://github.com/wasmi-labs/wasmi/issues/896.
Thread discussing the performance regressions in `wasmparser`: https://github.com/bytecodealliance/wasm-tools/issues/1701 --- Unfortunately benchmarks conducted locally show significant performance regressions for Wasm validation: We can see this clearly in the posted screenshot since...