Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior in fast-JIT mode and interpreter mode #3391

Closed
erxiaozhou opened this issue May 5, 2024 · 1 comment
Closed

Unexpected behavior in fast-JIT mode and interpreter mode #3391

erxiaozhou opened this issue May 5, 2024 · 1 comment
Labels
bug Something isn't working fast-jit fixed

Comments

@erxiaozhou
Copy link

Subject of the issue

The WAMR on fast interpreter mode / classic interpreter mode / fast JIT mode has a wrong execution result on the test case.

Test case

tt4.zip

Your environment

  • Host OS: Ubuntu 20.04
  • Commit Id: c0e33f0

Steps to reproduce

  1. build WAMR on fast interpreter mode / classic interpreter mode / fast JIT mode
  2. execute the command
iwasm --heap-size=0 -f "to_test" <test_case>

or

iwasm --heap-size=0  --fast-jit -f "to_test"

Expected behavior

No exception

Actual behavior

An exception " HashMap find elem failed: map or key is NULL."

wenyongh pushed a commit that referenced this issue May 9, 2024
In classic interpreter, fast interpreter and fast-jit running modes, set the local
variables' default value to NULL_REF (0xFFFFFFFF) rather than 0 if they are type
of externref or funcref.

The issue was reported in #3390 and #3391.
@wenyongh wenyongh added bug Something isn't working fixed fast-jit labels May 14, 2024
@wenyongh
Copy link
Contributor

Close the issue since it was fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fast-jit fixed
Projects
None yet
Development

No branches or pull requests

2 participants