Robin Freyler

I am going to close this issue since I don't think we should have SIMD support in `wasmi`. Those 10% saving in Wasm file sizes would not really solve our...

This architecture could be used to speed up instruction dispatch in `wasmi` with safe Rust code: https://github.com/Neopallium/s1vm

This article well describes different instruction dispatch techniques and their expected performance: https://www.complang.tuwien.ac.at/forth/threaded-code.html

Research into different instruction dispatch techniques implementable in Rust: https://github.com/Robbepop/interpreter-dispatch-research

PR merged to refactor the instruction dispatch for great wins: https://github.com/paritytech/wasmi/pull/376

Closed since all TODO items have been answered or resolved.

I am going to implement a more compact encoding of `wasmi` bytecode for the `v1` implementation introduced in https://github.com/paritytech/wasmi/pull/287.

The mentioned PR (https://github.com/paritytech/wasmi/pull/287) shrank the size of the `enum` bytecode from 24 bytes to 16 bytes by disentangling `BrTable` variant. The `BrCode` operand now only hosts the number of...

This issue is no longer relevant due to the fact that the current `wasmi` version is using Wasmtime based API which mostly is pretty well designed already.

Closing this issue since it is super old and probably equally outdated. Also the legacy `wasmi` engine for which this bug has been reported is no longer supported by us.