Differential `out of bounds` error in interpreter mode

[teyahb8]

Subject of the issue

I have generated a wasm binary as a test case which I ran with wasmtime, wamr (AOT mode), wamr (interpreter mode), and wasmedge runtimes. The wamr (WASM mode) runtime is producing an out of bounds error while the other runtimes are successfully executing the wasm module.

Test case

The .wat code, .wasm module, and the .aot files are attached here: files.zip

Your environment

• Host OS: Linux
• WAMR version 2.2.0, Linux, x86_64, interpreter mode

Steps to reproduce

1. Extract the test case archive
2. Run wat2wasm 528.wat
3. Run iwasm -f main 528.wasm

Expected behavior

Based on the differential behavior of wasmtime, wamr (AOT mode), and wasmedge runtimes, the expected behavior is to successfully execute the wasm module.

Actual behavior

The interpreter mode is causing out of bounds error.

Can you please confirm if this looks like a bug? Thanks in advance.

[TianlongLiang]

Yes, this is a bug due to type conversion, I created a PR here to fix this issue

[teyahb8]

I have checked. I am confirming the fix. I am closing the issue. Thanks for your prompt response.