This repository was archived by the owner on Nov 3, 2021. It is now read-only.
Clarify trapping semantics #50
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'm leaving the text for memory.copy as it is even though we've more or less agreed to remove the as-if intermediate buffer solution. Separate PR. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are clarifications of the trapping semantics for memory.fill, memory.init, and memory.copy, and thus also for table.init and table.copy. We clarify that there's a low->high write order and under what circumstances partially written data are observed.
This needs to be further elaborated once we agree on #49, but shouldn't be controversial at the moment.