Skip to content
This repository was archived by the owner on Nov 3, 2021. It is now read-only.

Update overview for the zero-byte OOB case #100

Merged
merged 1 commit into from
Jun 28, 2019
Merged

Update overview for the zero-byte OOB case #100

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions proposals/bulk-memory-operations/Overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,8 +277,6 @@ A trap occurs if:
active segments that were dropped after being copied into memory during module
instantiation.
* any of the accessed bytes lies outside the source data segment or the target memory
* the source offset is greater than the length of the source data segment
* the destination offset is greater than the length of the target memory

Note that it is allowed to use `memory.init` on the same data segment more than
once.
Expand Down Expand Up @@ -342,8 +340,6 @@ The instruction has the signature `[i32 i32 i32] -> []`. The parameters are, in

A trap occurs if:
* any of the accessed bytes lies outside the source or target memory
* the source offset is greater than the length of the source memory
* the destination offset is greater than the length of the target memory

A trap resulting from an access outside the source or target region
only occurs once the first byte that is outside the source or target
Expand All @@ -367,7 +363,6 @@ The instruction has the signature `[i32 i32 i32] -> []`. The parameters are, in

A trap occurs if:
* any of the accessed bytes lies outside the target memory
* the destination offset is greater than the length of the target memory

Filling takes place bytewise from lower addresses toward higher
addresses. A trap resulting from an access outside the target memory
Expand Down