Passing the component type to `wasm-component-ld` as WAT? · wit-bindgen

Stream: wit-bindgen

Topic: Passing the component type to `wasm-component-ld` as WAT?

Joel Dice (Jul 01 2024 at 18:36):

Per, https://github.com/dotnet/runtimelab/pull/2614#discussion_r1661386986, I've been adding WASIp2 support to .NET, and the current approach involves checking the wit-bindgen-generated bindings into source control (along with a script to regenerate them as desired), analogous to what we've done in wasi-libc.

However, the maintainers are concerned about the component type .o file being opaque and difficult to audit from a security perspective. Do we have other options for making that information available to wasm-component-ld, e.g. emitting a WAT file that could be passed directly to wasm-component-ld?

[NativeAOT-LLVM] support `System.Net.Http.HttpClient` on WASIp2 by dicej · Pull Request #2614 · dotnet/runtimelab

This adds WasiHttpHandler, a new implementation of HttpMessageHandler based on wasi:http/outgoing-handler, plus tweaks to System.Threading to allow async Tasks to work in a single-threaded context,...

Joel Dice (Jul 01 2024 at 18:38):

e.g. clang -Wl,--component-type=foo.wat ...

Joel Dice (Jul 02 2024 at 16:37):

I went ahead and opened an issue: https://github.com/bytecodealliance/wit-bindgen/issues/994

Support generating and using a human-readable form of the component type · Issue #994 · bytecodealliance/wit-bindgen

Per, dotnet/runtimelab#2614 (comment), I've been adding WASIp2 support to .NET, and the current approach involves checking the wit-bindgen-generated bindings into source control (along with a scrip...

Last updated: Dec 23 2024 at 12:05 UTC