Robin Freyler
Robin Freyler
Version: `rustfmt 1.8.0-nightly (75530e9f72 2025-03-18)` In my Wasmi project I have got the following Rust line of code: ```rust /// Executes an [`Instruction::CallImported`]. pub fn execute_call_imported( &mut self, store: &mut...
Closes https://github.com/wasmi-labs/wasmi/issues/1484.
Blocked by: https://github.com/wasmi-labs/wasmi/issues/1433 Currently Wasmi uses `wasmi_ir`'s `Instruction` enum for its simple instruction dispatch: https://github.com/wasmi-labs/wasmi/blob/1a31914028267a036be56c3d3af0e97a2efae924/crates/wasmi/src/engine/executor/instrs.rs#L134-L135 This is among the simplest solution for an interpreter execution implementation. IIRC this is also...
As the title suggests this is currently an unanswered question. This issue is about the idea to add a custom Wasm parsing crate to the Wasmi workspace: `wasmi_parse` The `wasmi_parse`...
Currently Wasm function details (i.e. `CompiledFunc` and `UncompiledFunc`) reside in Wasmi `Engine`'s `CodeMap`. ## Current Design: Pros & Cons ### Summary - Wasm functions and function types reside in the...
Currently we use a gigantic `macro_rules` macro in order to generate Wasmi's IR. See here: https://docs.rs/wasmi_ir/latest/src/wasmi_ir/for_each_op.rs.html In recent experiments I noticed that under certain cirumstance using a Cargo `build.rs` script...
Blocked by: https://github.com/wasmi-labs/wasmi/issues/1439 Currently Wasmi uses slices of `Instruction`s to represent function bodies. This is a very low level usage. A much better, more flexible and higher-level approach is build...
Wasmi's translator uses a simple linear register allocator. This is particularly easy since Wasmi provides up to 2^15 registers per function, so register spilling isn't even considered. However, this register...
There are proposed implementation defined limits for the Wasm JS API. I think it would probably be good if Wasmi imposes those same limits by default. Source: https://www.w3.org/TR/wasm-js-api-2/#limits