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

[meta] Support for the component model #450

Closed
7 of 14 tasks
fitzgen opened this issue Jan 20, 2022 · 4 comments
Closed
7 of 14 tasks

[meta] Support for the component model #450

fitzgen opened this issue Jan 20, 2022 · 4 comments
Labels
component-model Issues related to the implementation of the component model

Comments

@fitzgen
Copy link
Member

fitzgen commented Jan 20, 2022

Here is a list of what is required to migrate Bytecode Alliance projects to the new module linking spec that is based on the component model, rather than the old module linking spec that was based on core Wasm. Putting this list in the wasm-tools repo because most of the crates are here, and the work needs to start here. Let me know if I'm missing something and/or just edit this issue to add a checkbox for the missing item!

cc @peterhuene @alexcrichton @tschneidereit @lukewagner

@peterhuene
Copy link
Member

Thanks for putting this together, Nick!

I have a PR up for both wasm-encoder and wasmparser currently. An updated component model binary grammar is forthcoming soon, so I will revise both of those PRs with the new grammar as it should help reduce the complexity of those implementations greatly.

@peterhuene
Copy link
Member

As this work is disruptive to the existing module linking implementation and there will be, at times, the need to disable tests to land parts of the above work, we're going to land these changes in the component-model branch of this repository. A checkmark on the list above indicates the changes have been merged into the component-model branch.

Once the tools in this repo have been updated, tested, and fuzzed, we'll then think about the timing to merge the component-model branch into main.

@fitzgen
Copy link
Member Author

fitzgen commented May 5, 2022

Just a heads up: WebAssembly/component-model#29 will require a bunch of changes in the encoder, parser+validator, and wasm-smith.

@fitzgen fitzgen changed the title [meta] Support for module linking based on the component model, not on core Wasm [meta] Support for the component model Jun 23, 2022
@peterhuene peterhuene added the component-model Issues related to the implementation of the component model label Jul 25, 2022
@alexcrichton
Copy link
Member

I think this is done-enough at this point that I think this issue has served it's purpose and I'm going to close this. There are still remaining work items like wasm-mutate, wasm-smith, wizer, and wit-bindgen, but those are either going to get implemented on an as-needed basis or are so significant that tracking them here won't help them along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component-model Issues related to the implementation of the component model
Projects
None yet
Development

No branches or pull requests

3 participants