Here's a small getting started guide. Click here to start:
Please follow the installation instructions.
Wasm3 can also be used as a library for:
wasm3 passes the WebAssembly spec testsuite and is able to run many
Minimum useful system requirements: ~64Kb for code and ~10Kb RAM
wasm3 runs on a wide range of architectures (
ARC32, ...) and platforms:
|Webassembly Core Proposals||Extra|
|☑ Import/Export of Mutable Globals||☑ Structured execution tracing|
|☑ Non-trapping float-to-int conversions||☑ Big-Endian systems support|
|☑ Sign-extension operators||☑ Wasm and WASI self-hosting|
|☑ Multi-value||☑ Gas metering|
|☑ Bulk memory operations (partial support)||☑ Linear memory limit (< 64KiB)|
|☐ Multiple memories|
|☐ Reference types|
|☐ Tail call optimization|
|☐ Fixed-width SIMD|
|☐ Exception handling|
Why use a "slow interpreter" versus a "fast JIT"?
In many situations, speed is not the main concern. Runtime executable size, memory usage, startup latency can be improved with the interpreter approach. Portability and security are much easier to achieve and maintain. Additionally, development impedance is much lower. A simple library like Wasm3 is easy to compile and integrate into an existing project. (Wasm3 builds in a just few seconds). Finally, on some platforms (i.e. iOS and WebAssembly itself) you can't generate executable code pages in runtime, so JIT is unavailable.
Why would you want to run WASM on embedded devices?
Wasm3 started as a research project and remains so by many means. Evaluating the engine in different environments is part of the research. Given that we have
... running on MCUs,
WebAssembly is actually a promising alternative. It provides toolchain decoupling as well as a completely sandboxed, well-defined, predictable environment. Among practical use cases we can list
plugin systems, running
smart contracts, etc.
This project is released under The MIT License (MIT)