Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking issue for the bulk memory operations proposal #928

Closed
14 tasks done
fitzgen opened this issue Feb 7, 2020 · 1 comment
Closed
14 tasks done

Tracking issue for the bulk memory operations proposal #928

fitzgen opened this issue Feb 7, 2020 · 1 comment
Assignees
Labels
wasmtime Issues about wasmtime that don't fall into another label

Comments

@fitzgen
Copy link
Member

fitzgen commented Feb 7, 2020

This is a tracking issue for the bulk memory operations proposal.

TODO:

  • Enable the bulk memory proposal's test suite
    • binary.wast
    • bulk.wast
    • custom.wast
    • data.wast
    • elem.wast
    • imports.wast
    • linking.wast
    • memory_copy.wast
    • memory_fill.wast
    • memory_init.wast
    • table_init.wast
    • table_copy.wast
  • Enable bulk memory in the fuzzers
@fitzgen fitzgen self-assigned this Feb 7, 2020
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 14, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 14, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 14, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 24, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 24, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 26, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
fitzgen added a commit to fitzgen/wasmtime that referenced this issue Feb 26, 2020
This adds support for the `table.copy` instruction from the bulk memory
proposal. It also supports multiple tables, which were introduced by the
reference types proposal.

Part of bytecodealliance#928
@alexcrichton alexcrichton added the wasmtime Issues about wasmtime that don't fall into another label label Feb 27, 2020
@fitzgen
Copy link
Member Author

fitzgen commented Mar 11, 2020

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasmtime Issues about wasmtime that don't fall into another label
Projects
None yet
Development

No branches or pull requests

2 participants