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

remove JavaScript engine testing #89

Merged
merged 1 commit into from
Jun 17, 2016
Merged

Conversation

binji
Copy link
Member

@binji binji commented Jun 13, 2016

It's not really the appropriate place to handle it. Now that we have
wasm-wast and wasm-interp, we can at least verify that the tools are
internally consistent.

Resolves #79.

@@ -1,9 +1,6 @@
[submodule "third_party/testsuite"]
path = third_party/testsuite
url = https://github.com/WebAssembly/testsuite
[submodule "third_party/v8/v8"]
path = third_party/v8/v8
url = https://chromium.googlesource.com/v8/v8.git
[submodule "third_party/gtest"]
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't fully understand the purpose of gtest.
It looks like it is used to build hexfloat_test, which I can't find what this is used for.

Copy link
Member Author

Choose a reason for hiding this comment

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

My understanding is that older versions of MSVC (even 2013, I think?) don't support parsing hexadecimal floats via strtod. I implemented this (see wasm-literal.c), and wanted to add tests for it. hexfloat_test does exhaustive roundtrip testing of floats, and tests 4 billion doubles too. They don't run on Travis because they're kind of slow.

Copy link
Contributor

Choose a reason for hiding this comment

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

I see, thanks for the clarification

@Cellule
Copy link
Contributor

Cellule commented Jun 17, 2016

This looks good to me, pretty much the same changes I made when testing on my side.
👍

@binji binji force-pushed the remove-javascript-testing branch from b94e732 to abb190c Compare June 17, 2016 18:28
It's not really the appropriate place to handle it. Now that we have
wasm-wast and wasm-interp, we can at least verify that the tools are
internally consistent.
@binji binji force-pushed the remove-javascript-testing branch from abb190c to 12625a0 Compare June 17, 2016 18:34
@binji binji merged commit bb66db5 into master Jun 17, 2016
@binji binji deleted the remove-javascript-testing branch June 17, 2016 20:37
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