All issues

Search results

Tracking Phase 4 Requirements

Status: Open.

#50In WebAssembly/multi-memory;

· ashleynh opened on Sep 12, 2023

JS-API limits test still tests for limit of 1 memory

Status: Open.

#49In WebAssembly/multi-memory;

· backes opened on Aug 7, 2023

Toolchain support for multiple memories

Status: Open.

#45In WebAssembly/multi-memory;

· titzer opened on May 3, 2023

Use case for multi-memory: Sharing persistent datastructures between threads

Status: Open.

#43In WebAssembly/multi-memory;

· makoConstruct opened on Mar 1, 2023

Use-case for multi-memory: Less overhead tracking of store calls to facilitate networked rollback

Status: Open.

#42In WebAssembly/multi-memory;

· kettle11 opened on Feb 21, 2023

Use-case for multi-memory: Component Model object transfer browser polyfill

Status: Open.

#38In WebAssembly/multi-memory;

· eyebrowsoffire opened on Feb 2, 2023

Use-case for multi-memory: dart2wasm to implement ByteBuffer/TypedList objects with linear memory

Status: Open.

#37In WebAssembly/multi-memory;

· eyebrowsoffire opened on Feb 2, 2023

Use-case for multi-memory: Flutter Web Engine linking with wasm-compiled skia (C++) and ICU4X (Rust)

Status: Open.

#36In WebAssembly/multi-memory;

· eyebrowsoffire opened on Feb 2, 2023

Multi-Memory Lowering & Memory Imports

Status: Open.

#35In WebAssembly/multi-memory;

· ashleynh opened on Jan 3, 2023

Text format: parsing v128.loadX_lane and v128.storeX_lane requires backtracking

Status: Open.

#34In WebAssembly/multi-memory;

· tlively opened on Oct 21, 2022

Performance and memory use considerations

Status: Open.

#6In WebAssembly/multi-memory;

· lars-t-hansen opened on Nov 12, 2019