You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test case is expected to lead to an exception "unreachable". However, the warm on fast interpreter mode fails to raise the exception. Is it caused by the optimization in the fast interpreter?
#3482)
Fix several issues in wasm loader:
- Parse a block's type index with leb int32 instead leb uint32
- Correct dst dynamic offset of loop block arguments for opcode br
when copying the stack operands to the arguments of loop block
- Free each frame_csp's param_frame_offsets when destroy loader ctx
- Fix compilation error in wasm_mini_loader.c
- Add test cases of failed issues
This PR fixes issue #3467 and #3468.
Subject of the issue
The test case is expected to lead to an exception "unreachable". However, the warm on fast interpreter mode fails to raise the exception. Is it caused by the optimization in the fast interpreter?
Test case
tt_unreachable.zip
Your environment
Steps to reproduce
Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: