Different output number when running a same binary

[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. filea3891_2.zip

root@4252f5ec38df:/home/sxy/exp/1122/non_simd_1122# wamrc --bounds-checks=1 -o filea3891_2.wasm.aot filea3891_2.wasm ; iwasm --heap-size=0 -f main filea3891_2.wasm.aot
Create AoT compiler with:
  target:        x86_64
  target cpu:    znver3
  target triple: x86_64-unknown-linux-gnu
  cpu features:  
  opt level:     3
  size level:    3
  output format: AoT file
Compile success, file filea3891_2.wasm.aot was generated.
0x0:i32,0x2b5e6bb231e7a1dc:i64,0:f64

[TianlongLiang]

Hi, this should be due to the same reason as #2847. I will test it again once the modifications for #2847 are made.