Robin Freyler
Robin Freyler
Currently `wasmi_wasi` is stuck on `v2.0` of `wasi-common`, `wasi-cap-std-sync` and `wiggle` crate. For both `wasi-common` and `wiggle` [this PR](https://github.com/wasmi-labs/wasmi/pull/941) has shown that it is quite easy to update to the...
This is about adding support for the [`component-model` Wasm proposal](https://github.com/WebAssembly/component-model). The `component-model` Wasm proposal is still in early Phase 1 and thus stabilization cannot be expected to happen soon, however,...
Wasm producers such as LLVM often generate Wasm code with a so-called shadow stack in order to handle parameters and return values that did not fit the Wasm function parameter...
Currently Wasmi has no C bindings even though [the Wasm spec defines a C interface](https://github.com/WebAssembly/wasm-c-api) which could be implemented by Wasmi. The huge advantage is that this would open the...
Blocked by: https://github.com/paritytech/wasmi/issues/896, https://github.com/paritytech/wasmi/issues/894 Currently our differential fuzzer only supports Wasmi (register), Wasmi (stack) and Wasmtime. In https://github.com/paritytech/wasmi/issues/894 we found out that adding both Wasmer (Singlepass) and Wasmer (Cranelift) might...
Our latest attempts at improving the differential fuzzer led to a lot of technical debt which we should get rid of in order to properly implement both: - https://github.com/paritytech/wasmi/issues/894 -...
One big problem of our current differential fuzzing is that it reports false positives, i.e. it reports bugs for cases where the 3 Wasm engines, Wasmi (register), Wasmi (stack) and...
Currently when executing `wasmi` bytecode there is the so-called `InstanceCache` which caches data frequently used during `wasmi` bytecode execution such as the default `Memory` bytes. Whenever calling a function that...
The instruction sequence ```wat i64.{and,or,xor} i64.eqz i32.eqz {if, br_if} ``` Is very common. The `i64.eqz, i32.eqz` sequence acts as a double negative, thus nullifying itself. It exists for the purpose...
In the new `wasmi` register-machine translation we have to preserve values of `local.get x` registers if they are on the stack while an incoming `local.set x` or `local.tee x` overwrites...