Different output number when running a same binary， and memory.size may have problem

[XinyuShe]

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. filea22861_5.zip

This binary only has a main function, consisting of a total of 129 instructions. I found that wamr only executed the first 24 instructions. However, the inconsistency in stack value begins from the 8th instruction starting from 0, and the inconsistency in instruction_id (each instruction has an ID) starts from the 11th instruction starting from 0.

[TianlongLiang]

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.