Skip to content

Conversation

jcbeyler
Copy link

Seems like we never had an expected output for this test

Jean Christophe Beyler added 4 commits November 20, 2015 19:11
The loop1 method is too simple for LLVM, which then makes it return just 5.
Though this proves that the code is correct, we probably want to have the
  code generation all the same.

This patch makes a loop3 method based on loop1 so that the code ais  bit
  different but at least the compiler can no longer optimize it all away.

We've left loop1 to show the difference in compiler technologies
@jcbeyler jcbeyler closed this Dec 10, 2015
@jcbeyler
Copy link
Author

sorry, let me do this again

rossberg pushed a commit that referenced this pull request Jul 23, 2024
As discussed in #202

The JS tag was added to the JS API spec in #301, but it is not observable. This change
exposes it on the WebAssembly namespace, allowing it to be imported into wasm modules.
This allows wasm modules to explicitly extract the thrown JS objects as externrefs from the
caught exrefs, and also to throw fresh exceptions with externref payloads that will propagate 
into JS and can be caught as bare JS objects not wrapped in a WebAssembly.Exception.

It also places the restriction that WebAssembly.Exception objects cannot be created with
the JS tag, because it would result in ambiguity or asymmetry when such objects unwind
from JS into wasm and back out.
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.

1 participant