WebAssembly / WebAssembly/threads
Semantics of bulk memory operations
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 767
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
The semantics of bulk memory operations on shared linear memory seems to be currently underspecified. If the memory model is mostly the same as JS's, I assume these should be unordered atomic.
AFAICT V8's current implementation is also unsafe in that it just calls out to C memmove and memcpy under the hood, which are non-atomic.
@conrad-watt should know best.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's discussion of bulk memory operations on shared linear memory, the JavaScript memory-model comparison, and V8's use of C memmove and memcpy. Done means the semantics are specified clearly and the safety of the referenced implementation is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100