Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / WebAssembly/multi-memory issues and pull requests

#56 - Bump actions/download-artifact from 2 to 4.1.7 in /.github/workflows

Pull Request - State: closed - Opened by dependabot[bot] about 2 months ago
Labels: dependencies

#56 - Bump actions/download-artifact from 2 to 4.1.7 in /.github/workflows

Pull Request - State: closed - Opened by dependabot[bot] about 2 months ago
Labels: dependencies

#55 - Alignment test failure on the latest testsuite

Issue - State: closed - Opened by CharlieTap 2 months ago - 3 comments

#55 - Alignment test failure on the latest testsuite

Issue - State: closed - Opened by CharlieTap 2 months ago - 3 comments

#54 - Spec for instantiation of active data segments is incorrect

Issue - State: closed - Opened by CharlieTap 3 months ago - 1 comment

#54 - Spec for instantiation of active data segments is incorrect

Issue - State: closed - Opened by CharlieTap 3 months ago - 1 comment

#53 - Add missing memory specifier to memory.init execution semantics

Pull Request - State: closed - Opened by sbc100 4 months ago - 1 comment

#53 - Add missing memory specifier to memory.init execution semantics

Pull Request - State: closed - Opened by sbc100 4 months ago - 1 comment

#52 - A Bug in multi memory test?

Issue - State: closed - Opened by TianlongLiang 5 months ago - 2 comments

#52 - A Bug in multi memory test?

Issue - State: closed - Opened by TianlongLiang 5 months ago - 2 comments

#51 - Is there a way to access a non-hardcoded memory?

Issue - State: closed - Opened by Daniel-Abrecht 9 months ago - 2 comments

#50 - Tracking Phase 4 Requirements

Issue - State: open - Opened by ashleynh about 1 year ago - 8 comments

#50 - Tracking Phase 4 Requirements

Issue - State: open - Opened by ashleynh about 1 year ago - 8 comments

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

Issue - State: open - Opened by backes about 1 year ago

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

Issue - State: open - Opened by backes about 1 year ago

#48 - Clarify order of the memory.copy immediates

Pull Request - State: closed - Opened by backes over 1 year ago - 1 comment

#48 - Clarify order of the memory.copy immediates

Pull Request - State: closed - Opened by backes over 1 year ago - 1 comment

#47 - Implementation support

Issue - State: closed - Opened by eqrion over 1 year ago - 4 comments

#47 - Implementation support

Issue - State: closed - Opened by eqrion over 1 year ago - 4 comments

#46 - memory_copy1.wast: add some tests

Pull Request - State: closed - Opened by yamt over 1 year ago - 1 comment

#46 - memory_copy1.wast: add some tests

Pull Request - State: closed - Opened by yamt over 1 year ago - 1 comment

#45 - Toolchain support for multiple memories

Issue - State: open - Opened by titzer over 1 year ago - 31 comments

#45 - Toolchain support for multiple memories

Issue - State: open - Opened by titzer over 1 year ago - 31 comments

#44 - Rename new traps.wast test -> traps0.wast

Pull Request - State: closed - Opened by keithw over 1 year ago

#44 - Rename new traps.wast test -> traps0.wast

Pull Request - State: closed - Opened by keithw over 1 year ago

#41 - [test] Add more tests for multi-memory

Pull Request - State: closed - Opened by titzer over 1 year ago - 4 comments

#41 - [test] Add more tests for multi-memory

Pull Request - State: closed - Opened by titzer over 1 year ago - 4 comments

#40 - Separate simd tests to a separate file

Pull Request - State: closed - Opened by yamt over 1 year ago

#40 - Separate simd tests to a separate file

Pull Request - State: closed - Opened by yamt over 1 year ago

#39 - Additional test cases for multi-memory

Issue - State: closed - Opened by titzer over 1 year ago - 3 comments

#35 - Multi-Memory Lowering & Memory Imports

Issue - State: open - Opened by ashleynh almost 2 years ago - 1 comment

#35 - Multi-Memory Lowering & Memory Imports

Issue - State: open - Opened by ashleynh almost 2 years ago - 1 comment

#33 - Update spec for the load/store immediates binary format change.

Pull Request - State: closed - Opened by q82419 about 2 years ago - 2 comments

#33 - Update spec for the load/store immediates binary format change.

Pull Request - State: closed - Opened by q82419 about 2 years ago - 2 comments

#32 - Referencing locations across memories

Issue - State: closed - Opened by penzn about 2 years ago - 10 comments

#32 - Referencing locations across memories

Issue - State: closed - Opened by penzn about 2 years ago - 10 comments

#31 - A question about high level language interaction

Issue - State: closed - Opened by yamt over 2 years ago - 7 comments

#31 - A question about high level language interaction

Issue - State: closed - Opened by yamt over 2 years ago - 7 comments

#30 - Specify Memory Copy changes

Pull Request - State: closed - Opened by ashleynh over 2 years ago - 2 comments

#30 - Specify Memory Copy changes

Pull Request - State: closed - Opened by ashleynh over 2 years ago - 2 comments

#29 - Switch order of load/store immediates in binary format

Pull Request - State: closed - Opened by rossberg over 2 years ago

#29 - Switch order of load/store immediates in binary format

Pull Request - State: closed - Opened by rossberg over 2 years ago

#28 - Contradiction in multi-memory binary format instruction rules

Issue - State: closed - Opened by ashleynh over 2 years ago - 3 comments

#28 - Contradiction in multi-memory binary format instruction rules

Issue - State: closed - Opened by ashleynh over 2 years ago - 3 comments

#27 - Raise JS memory limit to 100

Pull Request - State: closed - Opened by rossberg almost 3 years ago - 1 comment

#27 - Raise JS memory limit to 100

Pull Request - State: closed - Opened by rossberg almost 3 years ago - 1 comment

#26 - Merge upstream

Pull Request - State: closed - Opened by rossberg almost 3 years ago

#26 - Merge upstream

Pull Request - State: closed - Opened by rossberg almost 3 years ago

#25 - Update text syntax to use `(memory $i)`

Pull Request - State: closed - Opened by alexcrichton almost 3 years ago - 3 comments

#25 - Update text syntax to use `(memory $i)`

Pull Request - State: closed - Opened by alexcrichton almost 3 years ago - 3 comments

#24 - Fix typo in multi-memory/Overview.md

Pull Request - State: closed - Opened by osa1 about 3 years ago

#24 - Fix typo in multi-memory/Overview.md

Pull Request - State: closed - Opened by osa1 about 3 years ago

#23 - Fix test

Pull Request - State: closed - Opened by rossberg about 3 years ago

#23 - Fix test

Pull Request - State: closed - Opened by rossberg about 3 years ago

#22 - Import wasmtime multi-memory test

Pull Request - State: closed - Opened by yhdengh about 3 years ago - 1 comment

#22 - Import wasmtime multi-memory test

Pull Request - State: closed - Opened by yhdengh about 3 years ago - 1 comment

#20 - Overlap with recent issue raised on the main WASM design repo

Issue - State: closed - Opened by cmuratori about 3 years ago - 5 comments

#20 - Overlap with recent issue raised on the main WASM design repo

Issue - State: closed - Opened by cmuratori about 3 years ago - 5 comments

#19 - Possibility to dynamically add memories at runtime?

Issue - State: closed - Opened by tomaka over 3 years ago - 2 comments

#19 - Possibility to dynamically add memories at runtime?

Issue - State: closed - Opened by tomaka over 3 years ago - 2 comments

#18 - Text syntax for SIMD lane index vs memory index operands

Issue - State: closed - Opened by AndrewScheidecker over 3 years ago - 1 comment

#18 - Text syntax for SIMD lane index vs memory index operands

Issue - State: closed - Opened by AndrewScheidecker over 3 years ago - 1 comment

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

Issue - State: closed - Opened by lars-t-hansen almost 4 years ago - 3 comments

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

Issue - State: closed - Opened by lars-t-hansen almost 4 years ago - 3 comments

#16 - Binary format is out of date

Issue - State: closed - Opened by titzer about 4 years ago - 3 comments

#16 - Binary format is out of date

Issue - State: closed - Opened by titzer about 4 years ago - 3 comments

#15 - Read only memories?

Issue - State: closed - Opened by icefoxen about 4 years ago - 11 comments

#15 - Read only memories?

Issue - State: closed - Opened by icefoxen about 4 years ago - 11 comments

#14 - [spec] Cherry-pick text format change from bulk-ops proposal

Pull Request - State: closed - Opened by rossberg about 4 years ago

#14 - [spec] Cherry-pick text format change from bulk-ops proposal

Pull Request - State: closed - Opened by rossberg about 4 years ago

#13 - Text format for data segments may be confusing with passive data segments

Issue - State: closed - Opened by alexcrichton about 4 years ago - 2 comments

#13 - Text format for data segments may be confusing with passive data segments

Issue - State: closed - Opened by alexcrichton about 4 years ago - 2 comments

#12 - Update syntax for elem/data to match bulk proposal

Pull Request - State: closed - Opened by rossberg over 4 years ago

#12 - Update syntax for elem/data to match bulk proposal

Pull Request - State: closed - Opened by rossberg over 4 years ago

#11 - Data segment syntax incompatible with bulk-memory-operations proposal

Issue - State: closed - Opened by Connicpu over 4 years ago - 1 comment

#11 - Data segment syntax incompatible with bulk-memory-operations proposal

Issue - State: closed - Opened by Connicpu over 4 years ago - 1 comment

#10 - How would multiple memories work with function imports?

Issue - State: closed - Opened by wcaughey over 4 years ago - 4 comments

#10 - How would multiple memories work with function imports?

Issue - State: closed - Opened by wcaughey over 4 years ago - 4 comments

#9 - Additional motivation: efficient memory mapping

Issue - State: closed - Opened by ratchetfreak over 4 years ago - 3 comments

#9 - Additional motivation: efficient memory mapping

Issue - State: closed - Opened by ratchetfreak over 4 years ago - 3 comments

#8 - Use case: Call stack sharing for microfunctions

Issue - State: closed - Opened by sffc over 4 years ago - 1 comment

#7 - Zero copy and 2D context

Issue - State: closed - Opened by penzn almost 5 years ago - 1 comment

#7 - Zero copy and 2D context

Issue - State: closed - Opened by penzn almost 5 years ago - 1 comment

#6 - Performance and memory use considerations

Issue - State: open - Opened by lars-t-hansen almost 5 years ago - 2 comments

#5 - [interpreter/test] Extend interpreter to multiple memories

Pull Request - State: closed - Opened by rossberg about 5 years ago - 2 comments

#4 - [js-api] Maximum number of memories

Issue - State: closed - Opened by rossberg about 5 years ago - 2 comments

#3 - [spec] Changes for multiple memories

Pull Request - State: closed - Opened by rossberg about 5 years ago - 1 comment

#2 - memarg encoding

Issue - State: closed - Opened by AndrewScheidecker about 5 years ago - 2 comments