We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
actch | 0x00 | tag : varuint32, label : varuint32 catch_ref | 0x01 | tag : varuint32, label : varuint32 catch_all | 0x02 | label : varuint32 catch_all_ref | 0x03 | label : varuint32
https://github.com/WebAssembly/exception-handling/blob/main/proposals/exception-handling/Exceptions.md It looks quite weird why the opcode of catch is 0x00. How does that work?
The text was updated successfully, but these errors were encountered:
Catches are part of try_table; in fact, they are actually immediates of a try_table instruction, so they don't have a separate "opcode".
try_table
Sorry, something went wrong.
so it is like
try_table catch 0x1f 0x00
?
so it is like try_table catch 0x1f 0x00 ?
try_table(1f) blocktype count catch(00) tag label
see https://webassembly.github.io/exception-handling/core/binary/instructions.html#control-instructions
No branches or pull requests
actch | 0x00 | tag : varuint32, label : varuint32
catch_ref | 0x01 | tag : varuint32, label : varuint32
catch_all | 0x02 | label : varuint32
catch_all_ref | 0x03 | label : varuint32
https://github.com/WebAssembly/exception-handling/blob/main/proposals/exception-handling/Exceptions.md
It looks quite weird why the opcode of catch is 0x00. How does that work?
The text was updated successfully, but these errors were encountered: