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

Adjust spec text to match bulk ops for element segment encoding #36

Closed
rossberg opened this issue Apr 3, 2019 · 1 comment
Closed

Adjust spec text to match bulk ops for element segment encoding #36

rossberg opened this issue Apr 3, 2019 · 1 comment
Assignees
@rossberg

Comments

@rossberg
Copy link
Member

rossberg commented Apr 3, 2019

Blocked on bulk ops proposal to finish spec text.
@rossberg rossberg self-assigned this Apr 3, 2019
@gahaas gahaas mentioned this issue May 27, 2019
Merged
@rossberg
Copy link
Member Author

Fixed via #46.

joyeecheung pushed a commit to joyeecheung/v8 that referenced this issue Jun 6, 2019
@gahaas
[wasm][anyref] Change element segment encoding
f6e3993 
The proposal is changing accordingly, see
WebAssembly/reference-types#36.

In our tests we were already using the new format implicitly, because
bulk-memory-operations are enabled by default. I noticed the missing
implementation when I executed spec tests with
--no-experimental-wasm-bulk-memory.

[email protected]

Bug: v8:7581
Change-Id: I13aaba9a8d60e8542245aac7f0a072da1be357dc
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1631591
Reviewed-by: Michael Starzinger <[email protected]>
Commit-Queue: Andreas Haas <[email protected]>
Cr-Commit-Position: refs/heads/master@{#61913}
rossberg pushed a commit that referenced this issue Nov 20, 2019
@binji
Two zero immediates for memory.copy and table.copy (#43)
178a7f6 
See #18, #29, and #36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rossberg rossberg

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rossberg