Skip to content

Conversation

sunfishcode
Copy link
Member

This is a PR against the void branch, which adds a few more tests.

Specifically, this tests constructs which merge values from two control paths, to ensure that the types match even when the resulting value is dropped.

"unknown label"
)

;; Test that the value operand of br_if matches the result type of the block
Copy link
Member

Choose a reason for hiding this comment

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

comment says br_if, but no br_if in test?

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed, thanks!

Fix the type of the condition of an if, so that the test tests what it's
supposed to test.
@rossberg
Copy link
Member

rossberg commented Jul 6, 2016

LGTM

@sunfishcode sunfishcode merged commit fa129a6 into void Jul 6, 2016
@sunfishcode
Copy link
Member Author

Merging with LGTM, and note that this is just on the void branch, rather than master at this time.

@sunfishcode sunfishcode deleted the void-more-tests branch July 19, 2016 17:52
ngzhian added a commit to ngzhian/spec that referenced this pull request Nov 4, 2021
This is sufficient to pass simd_f32x4.wast, simd_f32x4_arith.wast, and
simd_f32x4_cmp.wast.
rossberg pushed a commit that referenced this pull request Jul 23, 2024
This moves legacy JS API tests, which use the old `try` instruction,
into `test/legacy/js-api`. This also moves the legacy core tests from
`test/legacy` to `test/legacy/core`.
rossberg pushed a commit that referenced this pull request Jul 23, 2024
These two tests used to be in
https://github.com/WebAssembly/exception-handling/tree/main/test/js-api/exception
and were moved into
https://github.com/WebAssembly/exception-handling/tree/main/test/legacy/exceptions/js-api
in #305.

I'm planning new version of these tests that use `try_table` and
`throw_ref` in
https://github.com/WebAssembly/exception-handling/tree/main/test/js-api/exception,
but it wouldn't require to rewrite the whole tests, but copying these
tests into the this directory and modify them in a single PR makes
Github think these are brand-new files, resulting in a large diff
containing the whole files that is difficult to review (and which has
been reviewed and in the repo for a long time already).

So I'm making a PR that only re-adds these file here so that I can add
changes to these files in another PR.
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