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

About target *wasm32-wasip2-module* #426

Open
lum1n0us opened this issue Jun 10, 2024 · 2 comments
Open

About target *wasm32-wasip2-module* #426

lum1n0us opened this issue Jun 10, 2024 · 2 comments

Comments

@lum1n0us
Copy link
Contributor

I noticed an interesting concept in the slide of Wasm CG June 2024.

It said that add two targets in Preview 2, --target=wasm32-wasip2-component and --target=wasm32-wasip2-module. The latter is

easy to add to existing core wasm engines

I hope to get more details about that topic. Please give me a link or something else.

@loganek
Copy link

loganek commented Jun 10, 2024

Hi @lum1n0us I think the idea was briefly discussed in this ticket: WebAssembly/WASI#595 So basically the *-module is a foundational part for building the adapter, and the target in the linked discussion was called wasit2.

The primary difference between *-component and *-module in the context of the wasi-sdk IIUC is the linker (wasm-component-ld should be used to generate components, and wasm-ld for core modules). I'm not sure if those two should be a completely separate targets or one parametrized target (but I guess that's more an implementation detail).

@lum1n0us
Copy link
Contributor Author

thanks for that. wasit2 it is. Do you know any developing status about that work?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants