WebAssembly/multi-memory
View on GitHub ↗ ★ 139 WebAssembly archived
Multiple per-module memories for Wasm
11 mentions on Hacker News by 11 people: 0 stories, 11 comments · first 2020-01-19 · latest 2025-09-17
20082026
-
There has been a discussion ( https://github.com/WebAssembly/multi-memory/issues/45 ) on the toolchain support, but I'm not sure if there have been steps to use multiple address spaces to support Wasm multi-memory in LLVM yet.
comment by titzer · 2025-09-17 · in WASM 3.0 Completed -
…works in 'cross-origin isolated' contexts). There is a related 'multiple memories' proposal btw: https://github.com/WebAssembly/multi-memory
comment by flohofwoe · 2025-01-19 · in WASM GC isn't ready for realtime graphics -
Interesting! https://github.com/WebAssembly/multi-memory/blob/main/propos... The scaling point is what I was thinking of. "As long as Wasm memories are limited to 32 bit address space, there is no way to scale out of 4 GB memory…
comment by actionfromafar · 2024-11-28 · in Revisiting the DOS Memory Models -
…out, you would still need a way to represent your max heap size. Wasm also supports multimemories, https://github.com/WebAssembly/multi-memory
comment by sitkack · 2024-11-27 · in Revisiting the DOS Memory Models -
…it has horrible security (you don't know how the actually horrible security looks like). [1] https://github.com/WebAssembly/multi-memory/blob/main/propos...
comment by lifthrasiir · 2023-09-14 · in WASI Support in Go -
…mmap. This would definitely be nice to have, and it looks like the wasm authors agree with you. https://github.com/WebAssembly/multi-memory/issues/15
comment by josephg · 2023-08-05 · in WASI: WebAssembly System Interface -
…before it was dropped from 1.0. It looks like people are still working on that as the solution. https://github.com/WebAssembly/multi-memory > Add a memory index to all memory-related instructions. > Loads and stores have the memop field,…
comment by kevingadd · 2022-08-23 · in Accessing WebAssembly reference-typed arrays from C++ -
…And there's an active proposal to allow for multiple memories: https://github.com/WebAssembly/multi-memory/blob/main/propos... In an environment like that, you'd need full-fledged pointers to carry both the memory index a
comment by int_19h · 2022-06-28 · in WebAssembly and C++ -
The multi-memory proposal is your best bet for this: https://github.com/WebAssembly/multi-memory It's supported in Wasmtime, WAVM, and WABT and wasm2c, and not much else so far ( https://webassembly.org/roadmap/ ).
comment by keithwinstein · 2022-04-19 · in WebAssembly 2.0 First Working Draft -
Why prefer 64bit pointers over multiple memory address spaces ( https://github.com/WebAssembly/multi-memory )? Your CPU has to do a lot of work to keep pretending it's memory is flat, If we give up that pretense you can optimize cache…
comment by Avi-D-coder · 2020-05-14 · in Up to 4GB of Memory in WebAssembly -
…and extensions to get it beyond the mvp stage. [0]: https://github.com/WebAssembly/threads [1]: https://github.com/WebAssembly/multi-memory
comment by cdcarter · 2020-01-19 · in Standalone WebAssembly games using I/O devices