Robin Freyler

I was reading about memory load and store operation alignment semantics in Wasm and found this explanation: https://rsms.me/wasm-intro#addressing-memory So according to this source it seems to me that `wasmi` and...

@erxiaozhou it would be nice to know if you agree with my interpretation or disagree so we can either close this or find an agreement.

Hmmm, if this is true then it might imply a bug in the `wasmparser` crate with its Wasm validation infrastructure that we are also using in `wasmi`. Seems to be...

Interestingly trying to turn the Wasm file into a `.wat` file is also not possible due to the following error: ``` > wasm2wat replay_570_2_unexpected_execution.wasm -o replay_570_2_unexpected_execution.wat 0000046: error: invalid store...

@erxiaozhou I just tried your provided `wasmi_unexpected.wasm` with the most recent version of `wasmi_cli` and now it properly fails as expected denying the invalid alignment value. I guess the bug...

Strongly connected to this Wasmtime issue: https://github.com/bytecodealliance/wasmtime/issues/5344

The linked Wasmtime issue was just triaged and found to be fixed. (https://github.com/bytecodealliance/wasmtime/issues/5344#issuecomment-2395603696) Thus, once we update to the new `wasmparser` version we should have this fix ready for Wasmi...

`wasmtime run wasmi_nan.wasm --invoke to_test` prints `NaN` and `wasmi_cli wasmi_nan.wasm to_test` prints `NaN` as well. What else do you expect exactly? There is no differentiation between `+NaN` and `-NaN` in...

With respect to Wasm spec testsuite compliance for NaN values in `wasmi` I found that `wasmi`'s current spec testsuite is not 100% correct on the semantics of NaN value checking...

@erxiaozhou I just re-ran the above test with Wasmi v0.38.0 and got the following result: Original output of old Wasmi version from bug report: `00 00 00 2F 00 00...