Skip to content

Commit a00705b

Browse files
authored
Delete mentions of copying order in Overview.md (WebAssembly#134)
After the spec change in WebAssembly#126, byte copying order is not observable.
1 parent 82be3c0 commit a00705b

File tree

1 file changed

+2
-10
lines changed

1 file changed

+2
-10
lines changed

proposals/bulk-memory-operations/Overview.md

+2-10
Original file line numberDiff line numberDiff line change
@@ -320,16 +320,8 @@ written (by the copy operation) in the other region.
320320
This instruction has two immediate arguments: the source and
321321
destination memory indices. They currently both must be zero.
322322

323-
If the source region starts at a lower address than the target region, then the
324-
copy takes place as if from higher to lower addresses: the highest source
325-
address is read first and the value is written to the highest target address,
326-
then the next highest, and so on. Otherwise, the copy takes place as if from
327-
lower to higher addresses: the lowest source address is read first and the
328-
value is written to the lowest target address, then the next lowest, and so on.
329-
330-
(The direction of the copy is defined in order to future-proof
331-
`memory.copy` for shared memory and a memory read/write protection
332-
feature.)
323+
Copying takes place as if an intermediate buffer were used, allowing the
324+
destination and source to overlap.
333325

334326
The instruction has the signature `[i32 i32 i32] -> []`. The parameters are, in order:
335327

0 commit comments

Comments
 (0)