-
Notifications
You must be signed in to change notification settings - Fork 446
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
grow_memory takes page size #260
Conversation
lgtm |
lgtm |
Merging, with lgtms and no objections. |
grow_memory takes page size
|
||
(export "size_at_least" $size_at_least) | ||
(func $size_at_least (param i32) (result i32) (i32.ge_u (memory_size) (get_local 0))) | ||
(func $grow (param $sz i32) (result i32) (grow_memory (get_local $sz))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AstSemantics says this should be a multiple of the page size, but this sends in values like 1 which are meant to be multiplied by it. Which is wrong?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kripken It looks like WebAssembly/design#598 has not been merged which updated AstSemantics. People seemed to support changing grow_memory
to accept units of pages rather than bytes and there seems to be some support for also returning the new size in pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks.
Implement i16x8 operations
…h' (WebAssembly#260) * Adds validation algorithm case for `throw x`, adds missing x to 'catch' * Apply suggestions from code review Co-authored-by: Andreas Rossberg <rossberg@mpi-sws.org>
To go along with WebAssembly/design#598