Different execution time when running a same binary

[XinyuShe]

I use several runtimes to execute the same randomly generated WASM binary. Although they all report division by zero errors, the execution time of WAMR far exceeds that of other runtimes. filea373.zip

root@4252f5ec38df:/a# time wasmer run filea373.wasm  -i main --cranelift
error: failed to run `filea373.wasm`
╰─▶ 1: RuntimeError: out of bounds memory access
           at <unnamed> (filea373.wasm[1]:0xc9)
           at <unnamed> (filea373.wasm[2]:0x10c)

real    0m0.005s
user    0m0.000s
sys     0m0.004s
root@4252f5ec38df:/a# time /a/WasmEdge-0.13.5-Linux/bin/wasmedge_0.13.5  --reactor filea373.wasm main
[2023-11-26 19:12:29.055] [error] execution failed: out of bounds memory access, Code: 0x88
[2023-11-26 19:12:29.055] [error]     Accessing offset from: 0x100000f23 to: 0x100000f23 , Out of boundary: 0xffffffff
[2023-11-26 19:12:29.055] [error]     In instruction: i32.load8_s (0x2c) , Bytecode offset: 0x000000c9
[2023-11-26 19:12:29.055] [error]     When executing function name: "main"

real    0m0.015s
user    0m0.000s
sys     0m0.014s
root@4252f5ec38df:/a# time iwasm --heap-size=0 -f main --llvm-jit filea373.wasm
Exception: out of bounds memory access

real    0m55.423s
user    0m18.013s
sys     0m37.363s