Skip to content

Conversation

alexcrichton
Copy link
Contributor

This enables three proposals by default since they've been merged into
the upstream specification:

Most of the fallout from this is in the test suite with lots of
--enable flags getting removed and some tests which now
unconditionally pass also getting removed. Two spec tests explicitly
pass --disable until the spec test submodule is updated.

This enables three proposals by default since they've been merged into
the upstream specification:

* `saturating-float-to-int` - WebAssembly/spec#1143
* `sign-extension` - WebAssembly/spec#1144
* `multi-value` - WebAssembly/spec#1145

Most of the fallout from this is in the test suite with lots of
`--enable` flags getting removed and some tests which now
unconditionally pass also getting removed. Two spec tests explicitly
pass `--disable` until the spec test submodule is updated.
Copy link
Member

@binji binji left a comment

Choose a reason for hiding this comment

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

Thanks, lgtm! I was initially a little concerned about removing these tests, since I imagine folks will still want to test against MVP for a while. That said, I figure a better solution for that would be to keep a collection of MVP tests instead of maintaining them in wabt. So I'm OK with removing them.

@binji binji merged commit e88bc66 into WebAssembly:master May 6, 2020
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