Skip to content

WASM Exceptions And Tag Import/Export#362

Open
martindevans wants to merge 1 commit into
bytecodealliance:mainfrom
martindevans:tag_types_wasm_exceptions
Open

WASM Exceptions And Tag Import/Export#362
martindevans wants to merge 1 commit into
bytecodealliance:mainfrom
martindevans:tag_types_wasm_exceptions

Conversation

@martindevans
Copy link
Copy Markdown
Contributor

  • Added support for WASM tag types (import/export)
  • Added support for enabling WASM exceptions

This adds the ability to load modules which depend upon WASM exceptions. It does not add any support for catching, throwing or interacting with exceptions in any way (still working on that for a follow-up PR).

 - Added support for enabling wasm exceptions
@Avril112113
Copy link
Copy Markdown

I've been working on adding proper exceptions handling along with @martindevans (for a separate PR)
I've tested the tag import and exports in a project of mine, besides the tag Parameters, but the tests cover those anyway.

From prior testing, enabling exceptions in the config is no issue if there is no C# call boundary.
However, if there is a C# call boundary, a trap is triggered which boils all the way down in C# only, skipping WASM entirely.
So until the next PR, it's worth noting as it could be odd behaviour for WASM expecting to catch (for example, with setjmp/longjmp).

@jsturtevant
Copy link
Copy Markdown
Contributor

Is the next pr in flight? Should we wait on this or is it ready to go?

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.

3 participants