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 BigInt parameter in 16gb-wasm-memory tests #3696

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

backes
Copy link
Contributor

@backes backes commented Oct 2, 2024

The JS API for Memory was updated in WebAssembly/memory64#68 to require BigInt parameters.

@CLAassistant
Copy link

CLAassistant commented Oct 2, 2024

CLA assistant check
All committers have signed the CLA.

Copy link
Member

@kenrussell kenrussell left a comment

Choose a reason for hiding this comment

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

Thanks for this contribution. In the description, is it more accurate to say "...to require BigInt parameters when the Memory type is i64"?

If so - looks good to me as long as we update the message when this is merged.

Could we also say "Associated with Chromium bug crbug.com/370792790" in the description when merging? Welcome to mention any other browser bugs too.

Thanks in advance.

The JS API for Memory was updated in
WebAssembly/memory64#68 to require BigInt
parameters when the Memory type is i64.

Also see chromium-side failures (https://crbug.com/370792790).
@backes
Copy link
Contributor Author

backes commented Oct 4, 2024

Ack, I updated the commit message. Feel free to merge this any time.

@kenrussell
Copy link
Member

Discussed this in the WebGL WG meeting of 2024-10-03; as long as this is following the WebAssembly spec and has been tested in one implementation it seems fine to merge.

@kenrussell kenrussell merged commit 450cceb into KhronosGroup:main Oct 4, 2024
2 checks passed
@backes backes deleted the patch-1 branch October 7, 2024 10:55
@backes backes mentioned this pull request Nov 29, 2024
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