Tracking bug for the new exception handling proposal. The new proposal will be implemented behind a flag, on top of the old proposal. The main difference with the legacy exception handling proposal is the absence of a lexical rethrow. Instead, the catch handlers in a try-table block can push the caught exception on the stack as an exnref, and this exnref can be rethrown using the throw-ref instruction.
-- You received this message because: 1. The project was configured to send all issue notifications to this address
[wasm][exnref] Do not increment legacy EH use counter on 'throw'
The 'throw' instruction is the same in the legacy (eh) and new (exnref) proposal. Only count it as a use of the new proposal so that we can monitor the actual use count of the old proposal.
Stop generating catches after the first catch-all. This is syntactically allowed, but semantically a no-op. This fixes a bug in the Turboshaft interface. The next handler expects a new label in the try block, which the catch-all block does not create.
- Fix code printing by incrementing control depth. - Print number of entries for try_table. - Pop the related block when we leave a try_table scope. - Handle kExn, kNoExn in `GenerateRef`. - Implement `top_type` for kExn, kNoExn. - (Drive-by) Add line breaks to generated testcase.