[wasm] Jiterpreter implementation of CALL_HANDLER is incorrect

[kg]

When implementing a CALL_HANDLER opcode, the jiterpreter does not properly update the clause data before taking the branch. This means that (in theory) if a trace were to bail out from inside a finally block, the block's ENDFINALLY opcode would not branch to the correct place in the interpreter.
ENDFINALLY appears to properly check the clause data though.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

When implementing a CALL_HANDLER opcode, the jiterpreter does not properly update the clause data before taking the branch. This means that (in theory) if a trace were to bail out from inside a finally block, the block's ENDFINALLY opcode would not branch to the correct place in the interpreter.
ENDFINALLY appears to properly check the clause data though.

Author:	kg
Assignees:	-
Labels:	arch-wasm, area-Codegen-Interpreter-mono
Milestone:	-

[kg]

Reading the code again, I think it's correct, so I'm closing this