Skip to content

Conversation

@dhil
Copy link
Contributor

@dhil dhil commented Jan 21, 2026

This patch adds support for the resume_throw_ref instruction, which is similar to the resume_throw instruction, but rather than injecting a fresh exception into the continuation, the resume_throw_ref instruction injects an exception reference into the continuation.

Note: the new instruction is, at the time of writing, assigned the opcode 0xE5 conflicting with the switch instruction, which has been assigned 0xE6 as its opcode instead (c.f. the work-in-progress specification).

@dhil dhil requested a review from a team as a code owner January 21, 2026 17:13
@dhil dhil requested review from alexcrichton and removed request for a team January 21, 2026 17:13
This patch adds support for the `resume_throw_ref` instruction, which
is similar to the `resume_throw` instruction, but rather than
injecting a fresh exception into the continuation, the
`resume_throw_ref` instruction injects an exception reference into the
continuation.

Note: the new instruction is, at the time of writing, assigned the
opcode `0xE5` conflicting with the `switch` instruction, which has
been assigned `0xE6` as its opcode instead (c.f. [the work-in-progress
specification](https://github.com/WebAssembly/stack-switching/blob/main/proposals/stack-switching/Explainer.md#binary-format)).
@dhil dhil force-pushed the resume-throw-ref branch from fad2282 to 6d39d16 Compare January 21, 2026 17:21
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@alexcrichton alexcrichton added this pull request to the merge queue Jan 22, 2026
Merged via the queue into bytecodealliance:main with commit 7e9cf05 Jan 22, 2026
35 checks passed
@dhil dhil deleted the resume-throw-ref branch January 22, 2026 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants