WebAssembly/bulk-memory-operations

Issues

• [Support] Some legal grammar seems to be omitted by the official spec.

  #161 opened 4 years ago by 7ombie
  2

• Identifiers for passive segments

  #159 opened 4 years ago by 7ombie
  7

• Indexing any passive segments ahead of active segments, so indices are more intuitive.

  #160 opened 4 years ago by 7ombie
  2

• Clarify the order of memory.copy / table.copy

  #151 opened 5 years ago by binji
  7

• Clarify ref.null binary encoding

  #152 opened 5 years ago by binji
  1

• Incompatibility with long LEB128 form from the core spec

  #153 opened 5 years ago by RReverser
  12

• Clarification of encoding of element segment flags

  #156 opened 5 years ago by eqrion
  2

• Advance bulk-memory-operations to phase 4

  #132 opened 5 years ago by eqrion
  4

• Non-overlapping version of memory.copy?

  #121 opened 6 years ago by penzn
  13

• Should partial memory/table initializations after instantiation traps still be visible?

  #138 opened 5 years ago by fitzgen
  4

• Trapping on zero-length writes?

  #145 opened 6 years ago by rianhunter
  21

• Test suite doesn't work with new versions of wabt (assert_return_{canonical,arithmetic}_nan)

  #144 opened 6 years ago by rianhunter
  4

• Binary documentation out of date for memory.init

  #146 opened 6 years ago by rianhunter
  1

• Validation error or parse error when data count section value does not match data section count

  #142 opened 6 years ago by rianhunter
  1

• Slight instantiation incompatibility with MVP

  #133 opened 6 years ago by eqrion
  1

• Make `\funcelem` an administrative instruction

  #99 opened 6 years ago by binji
  1

• Repo website link is broken (404)

  #135 opened 6 years ago by AndrewScheidecker
  2

• Overview has stale information about encoding

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

• Zero-sized memory.init of dropped segments should trap

  #124 opened 6 years ago by tlively
  16

• Change passive element segment encoding

  #98 opened 6 years ago by binji
  11

• Simplify copy-direction check

  #96 opened 6 years ago by binji
  1

• Tests for passive element segments contain type

  #89 opened 6 years ago by gahaas
  2

• [soec] Add store typing and store extension rules for segment instances to Appendix

  #94 opened 6 years ago by rossberg
  1

• [spec] Make OOB spec changes to follow #123 and #126

  #127 opened 6 years ago by rossberg
  1

• [spec] Extend store typing in appendix with elem & data instances

  #128 opened 6 years ago by rossberg
  1

• memory.copy|fill semantics limit optimizations for short constant lengths

  #111 opened 6 years ago by eqrion
  53

• Allow zero-byte copy to be out-of-bounds

  #97 opened 6 years ago by binji
  6

• Update spec to allow dropping of passive segments

  #78 opened 6 years ago by rossberg
  1

• Spec lacks execution semantics for new instructions

  #76 opened 6 years ago by rossberg
  1

• Tests of memory.init in the absence of DataCount section

  #125 opened 6 years ago by sbc100
  2

• Naming of segments vs the table they belong to

  #122 opened 6 years ago by sbc100
  2

• Merge conflicts with spec master

  #112 opened 6 years ago by sunfishcode
  1

• Specify the immediate parameters of table.copy

  #117 opened 6 years ago by gahaas
  5

• Should `memory.init`/`drop` of active segments be a validation error?

  #107 opened 6 years ago by sbc100
  2

• Spec does not define data count section

  #73 opened 6 years ago by rossberg
  0

• Simplify flags

  #40 opened 6 years ago by rossberg
  8

• New instructions missing from spec's index

  #77 opened 6 years ago by rossberg
  0

• Spec still uses old names for data/elem.drop instructions

  #74 opened 6 years ago by rossberg
  1

• Is it a validation error to use memory.* if there is no memory?

  #79 opened 6 years ago by tlively
  4

• Coordinate encoding with reftypes proposal to take into account multiple tables

  #36 opened 7 years ago by lars-t-hansen
  7

• Split proposal into memory and table operations

  #47 opened 7 years ago by binji
  2

• Link to "instantiation" under memory.init is dead

  #55 opened 7 years ago by lars-t-hansen
  2

• References to wasm spec are incorrect in several ways

  #56 opened 7 years ago by lars-t-hansen
  2

• Precise semantics of memory.copy

  #49 opened 7 years ago by lars-t-hansen
  4

• Memory mapping?

  #52 opened 7 years ago by JakeSmarter
  3

• mem.init and mem.drop appear to break single-pass validation

  #27 opened 7 years ago by julian-seward1
  62

• Bikeshedding the documentation: rename active/passive segments?

  #37 opened 7 years ago by titzer
  2

• Reinterpreting memory indices as flags may not be backwards-compatible

  #34 opened 7 years ago by alexcrichton
  2

• table.copy overwriting behaviour

  #25 opened 7 years ago by julian-seward1
  2

• Inconsistent argument ordering for {memory,table}.init vs {memory,table}.copy

  #24 opened 7 years ago by julian-seward1
  0