wabt

Related: https://component-model.bytecodealliance.org/language-suppor... https://opencs.aalto.fi/en/courses/programming-languages/par... https://github.com/vivshaw/neurastheniacc https://github.com/WebAssembly/wabt

> WASM-as-IR .. (Is that a thing?) Yes, actually I've heard of some projects compiling a language to Wasm, then using wasm2c to translate to C. https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... The Zig project does something similar for their bootstrapping process with a custom wasm2c implementation with just the features they need. https://github.com/ziglang/zig/blob/master/stage1/wasm2c.c I get the feeling this is an underappreciated technique with more potential.

https://github.com/bytecodealliance/wasm-micro-runtime https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... ISTR Siemens uses wasm2c to compile Wasm for a bunch of embedded devices runninng Zephyr RTOS.

If you consider just Wasm 1.0 and 2.0, the amount of “runtime” is relatively sparse. A tool like wasm2c (or my wasm2go) shows this: there is no huge runtime to carry, just a fairly direct translation of Wasm byte code to C (or Go). wasm2c: https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... wasm2go: https://github.com/ncruces/wasm2go

It was very much the point to build everything from scratch. Though to be fair, for tests I am relying on https://github.com/WebAssembly/wabt

> And no, WebAssembly isn’t different. I just opened one of the examples you provided and tried to right-click to inspect element. Nothing happened. When I inspected the source a different way, all I found was an SVG for the logo and a JavaScript file to load the binary. When I inspected the DOM, all I found was a `<canvas>` the executable code draws into. What does that have to do with running the application? What user is going to inspect the elements of a web page? No end user will. Developers will, but that's got nothing to do with running the application. You can always go ahead and disassemble the .wasm file just like any other executable format. Here are some tools: https://github.com/WebAssembly/wabt If you're worried about understanding how an application works, remember that most of it is on the server side anyway. You won't hav

Yes, wasm2c implements the Wasm tail-call feature with trampolines, exactly this way. (https://github.com/WebAssembly/wabt/blob/main/test/wasm2c/ta... has an example.) Doing it with a trampoline is probably slower than if C really had tail calls. On the other hand, adding "real" tail calls to C would probably require changing the ABI (e.g. to "tailcc" or "fastcc -tailcallopt"), and I think there's some reason to think this would probably impose a penalty everywhere (https://llvm.org/docs/CodeGenerator.html#tail-call-optimizat...).

Hmmm…what about compiling to wasm, and/or then converting the wasm to C? https://github.com/wasm3/wasm3/releases/tag/v0.4.8 https://github.com/WebAssembly/wabt/tree/main/wasm2c

`wasm2c` fully implements the WebAssembly sandbox execution environment [0][1] and has the passing tests to prove it. To be a bit more specific, the .wasm binary you generate initially already has the WebAssembly semantics baked in (obviously) and `wasm2c` creates a portable C translation of the WebAssembly while also ensuring that the execution environment is sandboxed (e.g., the code traps when attempting out-of-bounds memory accesses). [0]: https://webassembly.org [1]: https://github.com/WebAssembly/wabt/issues/2289#issuecomment...

Wuffs is cool, but you can get similar results writing normal C library code, compiling it into a .wasm binary via Clang, and then running the .wasm binary through the `wasm2c` tool of the WebAssembly Binary Toolkit [0]. I personally prefer this method, although Wuffs will usually produce faster code. [0]: https://github.com/WebAssembly/wabt/tree/44837a7236e85c048de...

https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... is a straightforward way to take an untrusted application (compiled already to wasm) and turn it into C that you can embed into your application or compile to a linkable DLL. I believe this approach has been used to sandbox untrusted libraries in production by Mozilla: https://hacks.mozilla.org/2021/12/webassembly-and-back-again...

As long as this is happening, might as well try some of my favorites: https://github.com/wasm3/wasm3, https://github.com/WebAssembly/wabt, https://github.com/bytecodealliance/wasmtime

WASM: WebAssembly > Specification > Wasm program > Code representation > C source code and corresponding WebAssembly https://en.wikipedia.org/wiki/WebAssembly#Code_representatio... WASI: https://en.wikipedia.org/wiki/WebAssembly : > WebAssembly System Interface (WASI) is a simple interface (ABI and API) designed by Mozilla intended to be portable to any platform.[84] It provides POSIX-like features like file I/O constrained by capability-based security.[85][86] There are also a few other proposed ABI/APIs.[87][88] [88]: webassembly/wasm-c-api: https://github.com/WebAssembly/wasm-c-api /? WASM tutorial: https://www.google.com/search?q=wasm+tutorial /? WASM helloworld: https://www.google.com/search?q=wasm+helloworld Learn X in Y minutes > WebAssembly: https://learnxinyminutes.com/docs/wasm/ WebAssembly/WABT: The WebAssembly Binary Toolki

This seems sort of like understanding machine code vs assembly; it's much easier to learn WAT and translate to/from WASM as necessary using the wabt tools [0]. Either way its super cool how simple WebAssembly is, you can really get your hands dirty and understand exactly every detail of how your program runs! [0] https://github.com/WebAssembly/wabt