WP59: The wasm arena in a second, unexported memory
State: Proposed · Done: 0 of 4 · Design note: docs/wp59-wasm-arena-memory.md
Stages
- S1: a second memory added after
wasm-ldand exported asmemory, with the runtime's copy, fill and grow over it, behind a build flag - S2: every crossing (array and string arguments and results, host-import strings and windows, panic text, the storage mirror) goes through the exchange area
- S3: two memories the default for
--profile wasm-host, the Safari fallback, the rewritten forge test and the perf and size budget (owner's decisions) - S4: the security record: WH-10's "what stays" closed
Next
S1, the second memory: §3. Before it, check whether a forged trace descriptor reaches outside the arena (§10, question 1).
Waiting on a decision
How storage crosses (a mirror synced at the edges of a call, a memory bit per array, or a storage type of its own), how a page that must run in Safari gets a single-memory module, and how large the exchange area is under --memory (§8).
Not planned
Moving the arena out and leaving the program's memory exported, rewriting individual loads and stores after the link, dropping WH-10's bounds, shared memory.

