-
Notifications
You must be signed in to change notification settings - Fork 27
Advance bulk-memory-operations to phase 4 #132
Comments
Chrome/V8 indeed still needs to implement the latest bounds checking behavior. We should be done soon. |
binaryen also support bulk memory operations. Should it update bounds check validation? |
I think I filled in all the remaining gaps and tracked all the recent changes over the last few months -- at least as far as they were possible in isolation within this repo. Unfortunately, some pieces of spec (execution of table instructions, specifically) can only be completed properly in the presence of reference types. So I rebased that proposal repo on this one and filled in those parts over there. Technically, I'm afraid this means that we will need to merge both proposals together, since their semantics is mutually dependent. (Alternatively, we could duplicate various pieces of the reftypes spec here, but attempts to go that way got messy quickly, and would create a merging nightmare later.) |
This has been done a while ago. |
After the change and follow-ups for #124 it looks like all substantive issues with the design have been resolved. There are still some issues open regarding new instructions such as #13 and #121, however I think it would be prudent to leave those for another proposal if someone wishes to pursue them.
I'd like to propose then that we move this repo to phase 4.
Entry requirements:
The text was updated successfully, but these errors were encountered: