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

Add discussion about a max-memory-address-accessed hint alternative to the overview document #12

Merged
merged 1 commit into from
Apr 30, 2024

Conversation

fitzgen
Copy link
Collaborator

@fitzgen fitzgen commented Apr 25, 2024

This alternative approach was briefly discussed (and withdrawn) during the last CG meeting. The new text introduced in this commit expands on the discussion from the CG meeting and describes the advantages that allowing customization of the Wasm page size has over such a max-memory-address-accessed hint.

This alternative approach was briefly discussed (and withdrawn) during the last
CG meeting. The new text introduced in this commit expands on the discussion
from the CG meeting and describes the advantages that allowing customization of
the Wasm page size has over such a max-memory-address-accessed hint.
@fitzgen
Copy link
Collaborator Author

fitzgen commented Apr 30, 2024

Okay, its been a few days, I'm going to go ahead and merge this one.

@fitzgen fitzgen merged commit e3b15b5 into main Apr 30, 2024
@fitzgen fitzgen deleted the max-memory-address-accessed-hint branch April 30, 2024 16:50
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.

1 participant