-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Labels
wasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposalwasmtimeIssues about wasmtime that don't fall into another labelIssues about wasmtime that don't fall into another label
Description
This issue tracks anything incomplete with the effort to add shared memories started in #4187:
- wasm-smith: generate shared memory when
--threadsis present wasm-tools#624 - fuzz: allow generating shared memories #4266
- improve tests (@alexcrichton had a comment about trying to stress things by doing more in Wasm)
- add a
SharedMemoryTypeto thewasmtimeexternal API (@alexcrichton wanted this to disambiguate entirely between memories and shared memories - enable shared memory in the C API (Extend C API with interfaces needed to use threads #7940)
- shared memory: use shared memories with the pooling allocator #4244
- shared memory: no way to report memory growth failure #4240
- shared memory: audit safety of pointer copies in the presence of shared memories #4203
- shared memory: allow threads and memory64 proposals to coexist #4267
- shared memory: enable shared memory in differential_v8 fuzz target #4268
- Growth/creation of a shared memory is not subject to resource limiters
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
wasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposalwasmtimeIssues about wasmtime that don't fall into another labelIssues about wasmtime that don't fall into another label