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

[test] Check that memory is exported/imported with correct min limit after grow #1293

Merged
merged 1 commit into from
Apr 12, 2021

Conversation

gumb0
Copy link
Contributor

@gumb0 gumb0 commented Mar 5, 2021

I made this to check my understanding of the external memory definition in the spec:

image

IIUC it requires imported memory to have min limit equal to it's currently allocated size, which means it can be updated after grow, and that has implications on matching this memory limits against import definition in another module.

The test basically creates a module with (memory 1), grows it to 2 pages, then tries to import it into a module with (memory 2).
Then repeats it another time for the memory that is both imported and exported.

(It fails on WABT.)

Copy link
Member

@rossberg rossberg 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.

@gumb0
Copy link
Contributor Author

gumb0 commented Apr 12, 2021

@rossberg Is this going to be merged?

@rossberg rossberg merged commit b9668b9 into WebAssembly:master Apr 12, 2021
kateinoigakukun added a commit to kateinoigakukun/wasminspect that referenced this pull request Nov 4, 2021
@gumb0 gumb0 deleted the imported-memory-min branch September 26, 2022 13:54
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