erxiaozhou

> Couldn't reproduce this on arch64/M1. Will try on amd64 next. Yes, this is expected. it seems that the bug is x86 specific. This bug may have a similar root...

> Hi, thanks for spotting this, it really makes confusing, here s is 9, n is 0, and the length of data.data is 9 (note that the data segment index...

https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md Hi, I found another possible root cause for the difference. I found the instruction `memory.init` is designed to copy the `passive` data to the linear memory. However, in my...

> https://github.com/WebAssembly/bulk-memory-operations/blob/master/proposals/bulk-memory-operations/Overview.md > > Hi, I found another possible root cause for the difference. I found the instruction `memory.init` is designed to copy the `passive` data to the linear memory....

Thank you for your reply! I will try to test it these days.

Hi, the bug has not been triggered again in my testing. It looks good.

> Hi, the reason you get both the error message `fast jit compilation failed: Error: unsupported opcode` and the successful execution result `:v128` is you are using the Multi-tier JIT...

I have tried multiple tools to execute the test case: - wasmtime-cli 17.0.0 (37300d3f4 2023-12-20) - wasm-validate (git~1.0.32-66-gfb31c1a2) - wasmedge 0.13.5-73-ge41eb56b and they all reported the similar content indicating the...

> Hi, I think this bug is because of spec update, I used the low version wabt and there is the same exception. I will look into it. @TianlongLiang Wamr...

It seems that this issue and https://github.com/bytecodealliance/wasm-micro-runtime/issues/3061 suffer from the same root cause.