-
Notifications
You must be signed in to change notification settings - Fork 578
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 exception on fast interpreter mode #3401
Labels
Comments
@erxiaozhou thanks for reporting the issue, please try #3434. |
wenyongh
added a commit
that referenced
this issue
May 15, 2024
When copying two cells from src offsets to dst offsets in RECOVER_BR_INFO, the offsets may be overlapped and the src data may be overwritten, use GET_I64_FROM_ADDR and then SET_I64_FROM_ADDR instead to resolve it. And handling VALUE_TYPE_FUNCREF/VALUE_TYPE_EXTERNREF for opcode local.set and local.tee when reference types feature is enabled. This PR fixes issue #3401 and #3402.
erxiaozhou
changed the title
Unexpected exception on faster interpreter mode
Unexpected exception on fast interpreter mode
May 16, 2024
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
Subject of the issue
WAMR on fast interpreter mode raises an exception indicating "invalid local type" on a valid case.
Test case
f64.const_6LLPBLPP_856_1714940342309342.zip
Your environment
Steps to reproduce
Expected behavior
No exception
Actual behavior
An exception
The text was updated successfully, but these errors were encountered: