WAMR behaves differently compared to other runtimes for a particular test case.

[ihayet]

Subject of the issue

WAMR behaves differently compared to other runtimes for a particular test case.

Test case

Uploaded files.zip contains the wat code, the wasm binary, and the aot file. files.zip

Your environment

• WAMR version (2.2.0), platform (Darwin), cpu architecture (X86_64), running mode (AOT).

Steps to reproduce

Run wat2wasm 14.wat to produce 14.wasm
Run wamrc --bounds-checks=1 -o 14.aot 14.wasm to generate 14.aot
Run iwasm -f main 14.aot to manifest the crash

Expected behavior

Outputs from the other runtimes are as follows:

wasmtime output:

NaN
0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009303770844854126
340282366920899777837155946497432354815

wasmer output:

NaN 0.00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009303770844854126 340282366920899777837155946497432354815

wasmedge output:

-nan
9.303770844854126e-209
340282366920899777837155946497432354815

Actual behavior

Outputs from wamrc and iwasm are as follows:

wamrc output:

Create AoT compiler with:
  target:        x86_64
  target cpu:    skylake
  target triple: x86_64-pc-linux-gnu
  cpu features:  
  opt level:     3
  size level:    1
  output format: AoT file
Compile success, file 14.aot was generated.

iwasm output:

unhandled SIGSEGV, si_addr: 0x0

Can you confirm if this is a bug? Thanks in advance.