Skip to content
New issue

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

Use assert_return_nan for test of fxx.min and fxx.max with nan inputs. #315

Merged
merged 2 commits into from
Aug 2, 2016

Conversation

gahaas
Copy link
Collaborator

@gahaas gahaas commented Aug 2, 2016

The spec tests for f32.min, f32.max, f64.min, and f64.max with NaN inputs were more strict than required by the design doc. The changes in this PR adjust these spec tests to the requirements in the design doc.

@sunfishcode
Copy link
Member

LGTM.

The NaN propagation semantics have changed, and the tests have not been updated for the changes in general. This PR for min/max is a good start.

@rossberg rossberg merged commit dbe7af1 into WebAssembly:master Aug 2, 2016
ngzhian added a commit to ngzhian/spec that referenced this pull request Nov 4, 2021
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