Skip to content

Updates for Memory64 proposal tests from latest testsuite #1560

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

Merged
merged 1 commit into from
Oct 26, 2020

Conversation

aardappel
Copy link
Contributor

This involves changes for Memory64, SIMD, and misc others.

WiP - No need to review yet.. trying to test with CI

@aardappel aardappel mentioned this pull request Oct 15, 2020
@aardappel
Copy link
Contributor Author

This PR is similar to #1553, but also fixes Memory64 problems. It doesn't yet fix all the SIMD problems the other PR fixes, though. And neither one knows how to fix the func.wast related problems uniformly.

@binji
Copy link
Member

binji commented Oct 21, 2020

It seems like it may be better to land #1553, then land this change on top. The func.wast issues are probably best to fix in another PR.

@binji
Copy link
Member

binji commented Oct 26, 2020

Now that #1553 landed, would you mind updating this PR?

These uncovered some things the previous tests didn't!
Also required the switching of the location of the index as discussed in WebAssembly/memory64#5
Also one small .py change that ensures the new tests have consistent posix paths.
@aardappel aardappel changed the title [WiP] Changes required for latest testsuite commit Updates for Memory64 proposal tests from latest testsuite Oct 26, 2020
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.

lgtm!

@aardappel aardappel merged commit 8e42376 into WebAssembly:master Oct 26, 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