Skip to content
Bulk memory operations
Branch: master
Clone or download
binji [spec] Use optional data instance, not data address (#93)
data.drop must update the store, not the frame. There may be multiple
copies of the frame, so any updates will only update once. We can make
sure that all copies are updated by using an indirection through data
addresses and updating the store instead.

See discussion in PR #92.
Latest commit 80aea4a Jun 8, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
document [spec] Use optional data instance, not data address (#93) Jun 8, 2019
interpreter
papers Rectify licensing (#496) Jun 13, 2017
proposals/bulk-memory-operations Init/copy/fill with offsets at the end of the memory or table (#86) May 13, 2019
test Fix merge conflicts introduced w/ PRs #84 and #86 (#87) May 13, 2019
.gitattributes Adjust .gitattribute Mar 22, 2017
.gitignore [infra] Update .gitignore Jul 31, 2017
.gitmodules Update katex to v0.10.0 (#949) Jan 24, 2019
.travis.yml
Contributing.md Fix an obvious broken link. Aug 13, 2015
LICENSE
README.md Combine bulk-memory-ops + cond-seg-init proposals (#5) Jan 18, 2018
deploy_key.enc Improve build and fix typos (#628) Jan 3, 2018
w3c.json

README.md

Build Status

Bulk Memory Operations Proposal for WebAssembly

This repository is a clone of github.com/WebAssembly/spec/. It is meant for discussion, prototype specification and implementation of a proposal to add bulk memory operations (e.g. instructions with behavior similar to memmove and memset) to WebAssembly.

See the overview for a summary of the proposal.

Original README from upstream repository follows...

spec

This repository holds the sources for the WebAssembly draft specification (to seed a future WebAssembly Working Group), a reference implementation, and the official testsuite.

A formatted version of the spec is available here: webassembly.github.io/spec,

Participation is welcome. Discussions about new features, significant semantic changes, or any specification change likely to generate substantial discussion should take place in the WebAssembly design repository first, so that this spec repository can remain focused. And please follow the guidelines for contributing.

You can’t perform that action at this time.