wasm-micro-runtime
wasm-micro-runtime copied to clipboard
Different output number when running a same binary
I used the AOT mode of different runtimes to run randomly generated wasm binaries, and the output number from WAMR was different from the others.
I instrumented the binary and found an inconsistency in the stack value of the memory.grow instruction.
Hi, this should be due to the same reason as https://github.com/bytecodealliance/wasm-micro-runtime/issues/2847. I will test it again once the modifications for https://github.com/bytecodealliance/wasm-micro-runtime/issues/2847 are made.