WebAssembly/multi-memory

Issues

• Toolchain support for multiple memories

  #45 opened 2 years ago by titzer
  31

• Alignment test failure on the latest testsuite

  #55 opened 4 months ago by CharlieTap
  3

• Spec for instantiation of active data segments is incorrect

  #54 opened 5 months ago by CharlieTap
  1

• A Bug in multi memory test?

  #52 opened 6 months ago by TianlongLiang
  2

• Is there a way to access a non-hardcoded memory?

  #51 opened 10 months ago by Daniel-Abrecht
  2

• Additional test cases for multi-memory

  #39 opened a year ago by titzer
  3

• Implementation support

  #47 opened a year ago by eqrion
  4

• Tracking Phase 4 Requirements

  #50 opened a year ago by ashleynh
  8

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

  #38 opened 2 years ago by eyebrowsoffire
  2

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

  #49 opened a year ago by backes
  0

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

  #37 opened 2 years ago by eyebrowsoffire
  8

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

  #36 opened 2 years ago by eyebrowsoffire
  5

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

  #43 opened 2 years ago by makoConstruct
  0

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

  #42 opened 2 years ago by kettle11
  1

• Multi-Memory Lowering & Memory Imports

  #35 opened 2 years ago by ashleynh
  1

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

  #34 opened 2 years ago by tlively
  6

• Additional motivation: efficient memory mapping

  #9 opened 2 years ago by ratchetfreak
  3

• Referencing locations across memories

  #32 opened 2 years ago by penzn
  10

• A question about high level language interaction

  #31 opened 2 years ago by yamt
  7

• Contradiction in multi-memory binary format instruction rules

  #28 opened 2 years ago by ashleynh
  3

• How is a non-default memory index to be denoted in the text format?

  #17 opened 2 years ago by lars-t-hansen
  3

• [js-api] Maximum number of memories

  #4 opened 3 years ago by rossberg
  2

• Zero copy and 2D context

  #7 opened 3 years ago by penzn
  1

• Read only memories?

  #15 opened 3 years ago by icefoxen
  11

• Possibility to dynamically add memories at runtime?

  #19 opened 3 years ago by tomaka
  2

• Binary format is out of date

  #16 opened 3 years ago by titzer
  3

• Overlap with recent issue raised on the main WASM design repo

  #20 opened 3 years ago by cmuratori
  5

• Text syntax for SIMD lane index vs memory index operands

  #18 opened 4 years ago by AndrewScheidecker
  1

• Text format for data segments may be confusing with passive data segments

  #13 opened 4 years ago by alexcrichton
  2

• Data segment syntax incompatible with bulk-memory-operations proposal

  #11 opened 5 years ago by Connicpu
  1

• How would multiple memories work with function imports?

  #10 opened 5 years ago by wcaughey
  4

• Use case: Call stack sharing for microfunctions

  #8 opened 5 years ago by sffc
  1

• Performance and memory use considerations

  #6 opened 5 years ago by lars-t-hansen
  2

• memarg encoding

  #2 opened 5 years ago by AndrewScheidecker
  2

• Memory index immediate vs. operand

  #1 opened 5 years ago by pepyakin
  4