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

[asyncify] Refactor argument restoring under wasm64. NFC #21984

Merged
merged 1 commit into from
May 23, 2024

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented May 23, 2024

This change was split out from my larger change to switch to table64.

When we use MEMORY64 + ASYNCIFY=1 we have add multiple wrappers to the wasm exports. This change basically moves the argument restoration to the outside rather than doing int the wrapper. This means that all the different wrappers see the restored arguments, not just the asyncify wrapper (which is the first/lowest level wrapper.

This change was split out from my larger change to switch to table64.

When we use MEMORY64 + ASYNCIFY=1 we have add multiple wrappers to the
wasm exports.  This change basically moves the argument restoration to
the outside rather than doing int the wrapper.  This means that all the
different wrappers see the restored arguments, not just the asyncify
wrapper (which is the first/lowest level wrapper.
@sbc100 sbc100 merged commit 0c5cb79 into emscripten-core:main May 23, 2024
29 checks passed
@sbc100 sbc100 deleted the asynficy_table64 branch May 23, 2024 17:45
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.

None yet

3 participants