Wasm30 is the fork o the efficient wasm interpreter Wasm3, made by Volodymyr Shymanskyy πΊπ¦.
This new branded fork was born from the need to run wasm binaries on the limited resources of the ESP32. Given this, at the moment WASM30 can be heavily dependent on the ESP-IDF environment.
The first peculiarity of WASM30 compared to WASM3 is to have specialized the M3Memory
class (in the file m3_segmented_memory.c
) to support data segmentation and, consequently, segment paging with real-time storage and retrieval in case of need during runtime.
To have a practical implementation of WASM30 in a ESP32 architecture, take a look to the HelloESP repo. In the repo are present also practical examples about how implement native functions in the WASM runtime in files he_wasm.c
and he_wasm_native.c
.
A part the segmented memory support, WASM30 aims to implement the Memory64 specifications also inside 32 bit architectures. This complete fork is also necessary due to the heavy modification of the original code, that makes a merge to the original project impossible.
Work in progress by Riccardo Cecchini (cekkr)
Note
I regret to inform the community that since my house was destroyed by russians who invaded my country, Wasm3 will enter a minimal maintenance phase. At this time, I am unable to continue the development of new features. However, I am committed to keeping the project alive and will actively review and merge incoming Pull Requests. I deeply appreciate your understanding and support during this difficult period. Your contributions to Wasm3 are now more valuable than ever.
A fast WebAssembly interpreter and the most universal WASM runtime.
Based on CoreMark 1.0 and independent benchmarks. Your mileage may vary.
Please follow the installation instructions.
Wasm3 can also be used as a library for:
Python3 β
Rust β
C/C++ β
D β
GoLang β
Zig β
Perl
Swift β
.Net β
Nim β
Arduino, PlatformIO, Particle β QuickJS
wasm3
passes the WebAssembly spec testsuite and is able to run many WASI
apps.
Minimum useful system requirements: ~64Kb for code and ~10Kb RAM
wasm3
runs on a wide range of architectures (x86
, x86_64
, ARM
, RISC-V
, PowerPC
, MIPS
, Xtensa
, ARC32
, ...) and platforms:
Linux,
Windows,
OS X,
FreeBSD,
Android,
iOS
OpenWrt, Yocto, Buildroot (routers, modems, etc.)
Raspberry Pi, Orange Pi and other SBCs
MCUs: Arduino, ESP8266, ESP32, Particle, ... see full list
Browsers. Yes, using WebAssembly itself!
wasm3
can executewasm3
(self-hosting)
Webassembly 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) |
β Custom page size | |
β³ Multiple memories | |
β³ Reference types | |
β Tail call optimization | |
β Fixed-width SIMD | |
β Exception handling | |
β Stack Switching |
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 any means. Evaluating the engine in different environments is part of the research. Given that we have Lua
, JS
, Python
, Lisp
, ...
running on MCUs, WebAssembly
is a promising alternative. It provides toolchain decoupling as well as a completely sandboxed, well-defined, predictable environment. Among practical use cases we can list edge computing
, scripting
, plugin systems
, running IoT rules
, smart contracts
, etc.
γ
γ
γ
γ
γ
γ
γ
γ
γ
γ
γ
γ
Demos
Installation instructions
Cookbook
Troubleshooting
Build and Development instructions
Supported Hardware
Testing & Fuzzing
Performance
Interpreter Architecture
Logging
Awesome WebAssembly Tools
This project is released under The MIT License (MIT)