Component model support

[steren]

WASI has moved to preview 2, which is based on the Component Model.

In a recent community presentation, it was briefly mentioned that the component model would be in WAMR's roadmap, but I wasn't able to find an issue or more written information about this topic. I suggest using this issue as a feature request and as a way to attach any existing links to plans and timelines for this topic.

[yamt]

technically, preview2 does not require component model.
i agree it's nice to have component model though.

btw, to make component model useful, i suspect we need to align our import/export model to the standard semantics (cf. #1353)
because many of the current use cases of component model involves import/export heavily.

[lum1n0us]

btw, to make component model useful, i suspect we need to align our import/export model to the standard semantics

Yes, need fully alignment firstly.

[squillace]

I'm extremely interested in preview 2 and component model support in wamr for our usage. Love to hear thinking on how to help this out with wamr.

[lum1n0us]

@squillace I am not sure about that. But would you mind sharing your usage about preview2 and component model. Since all I've heard about it are kinds of concern, and you are the first one to stand for it.

[nilslice]

+1 on interest in @squillace use case! happy to try to find ways to support via contribution here.

[trcrsired]

how does preview2 work without component model? How does it know whether it is 32bit wasm or 64bit wasm?

[weiyuemin]

Any update on this? It sounds great to have component model in wamr

[lum1n0us]

There isn't a set timetable for the component model at this time. However, we are getting ready for it. Like by restructuring the code base through the implementation of instantiation linking. We are open to any advanced plans on how to effectively support the component model and how to correctly integrate the component model into the embedded world.

[GordonSmith]

Not sure if it is of interest, but I started work on a C++ ABI implementation of the component model here: https://github.com/GordonSmith/component-model-cpp
I am trying to keep it runtime agnostic and am using it as an excuse to get used to some of the newer C++language features...

[lum1n0us]

Excellent. I'm looking forward to seeing an example.

[GordonSmith]

Just working through some initial samples - plenty of work todo, but hopefully you can see the use pattern take shape:

• wit: https://github.com/GordonSmith/component-model-cpp/blob/trunk/samples/wasm/sample.wit
• wamr: https://github.com/GordonSmith/component-model-cpp/blob/trunk/samples/wamr/main.cpp#L171-L265

Output:

and_func(0, 0): 0
and_func(0, 1): 0
and_func(1, 0): 0
and_func(1, 1): 1
add_func(3.1, 0.2): 3.3
reverse_string(Hello World!): !dlroW olleH
reverse_string(!dlroW olleH): Hello World!
reverse_tuple(0, Hello World!): !dlroW olleH, 1
list_filter_bool(2): 1

[rinthnoid]

Is there any progress towards WAMR wasip2/component model since it is interesting feature yet to come in other runtimes except only wasmtime. And also the wasmtime is very hard to compile for android operating system.
It would be far more than nice if WAMR able support the component model wasm modules.

[srberard]

One thing discussed in the e-SIG was to explore using a similar approach as with JCO. That is, preprocess the Wasm Component file into a Core Wasm module which is runnable on any Wasm runtime including WAMR (If I understand correctly, there is support changes required to the runtime as well). Gravity did something similar with the Wazero runtime. If there is interest in this approach, I'd be happy to set up a discussion to see what this might involve.