WebAssembly Micro Runtime
A Bytecode Alliance project
WebAssembly Micro Runtime (WAMR) is a standalone WebAssembly (WASM) runtime with a small footprint. It includes a few parts as below:
The "iwasm" VM core, supporting WebAssembly interpreter, ahead of time compilation (AoT) and Just-in-Time compilation (JIT)
The application framework and the supporting API's for the WASM applications
The dynamic management of the WASM applications
iwasm VM core
- 100% compliant to the W3C WASM MVP
- Small runtime binary size (85K for interpreter and 50K for AoT) and low memory usage
- Near to native speed by AoT
- Self-implemented module loader enables AoT working cross Linux, SGX and MCU systems
- Choices of WASM application libc support: the built-in libc subset for the embedded environment or WASI for standard libc
- Embeddable with the supporting C API's
- The mechanism for exporting native API's to WASM applications
- Multiple modules as dependencies, ref to sample
- Thread management and pthread library, ref to sample
- Linux SGX (Intel Software Guard Extension) support
- Source debugging
- Non-trapping float-to-int conversions
- Sign-extension operators
- Bulk memory operations
- Shared memory
- wasm-c-api, ref to document and sample
- 128-bit SIMD, ref to samples/workload
- Reference Types, ref to document and sample
Supported architectures and platforms
The iwasm supports the following architectures:
- X86-64, X86-32
- ARM, THUMB (ARMV7 Cortex-M7 and Cortex-A15 are tested)
- AArch64 (Cortex-A57 and Cortex-A53 are tested)
- RISCV64, RISCV32 (RISC-V LP64 and RISC-V LP64D are tested)
Following platforms are supported. Refer to WAMR porting guide for how to port WAMR to a new platform.
- Linux, Linux SGX (Intel Software Guard Extension), MacOS, Android, Windows
- Zephyr, AliOS-Things, VxWorks, NuttX, RT-Thread
Build iwasm VM core (mini product)
WAMR supports building the iwasm VM core only (no app framework) to the mini product. The WAMR mini product takes the WASM application file name or AoT file name as input and then executes it. For the detailed procedure, please see build WAMR VM core and build and run WASM application. Also we can click the link of each platform above to see how to build iwasm on it.
Build wamrc AoT compiler
Both wasm binary file and AoT file are supported by iwasm. The wamrc AoT compiler is to compile wasm binary file to AoT file which can also be run by iwasm. Execute following commands to build wamrc compiler for Linux:
cd wamr-compiler ./build_llvm.sh (or "./build_llvm_xtensa.sh" to support xtensa target) mkdir build && cd build cmake .. (or "cmake .. -DWAMR_BUILD_PLATFORM=darwin" for MacOS) make # wamrc is generated under current directory
cd wamr-compiler python build_llvm.py mkdir build && cd build cmake .. cmake --build . --config Release # wamrc.exe is generated under .\Release directory
By using the iwasm VM core, we are flexible to build different application frameworks for the specific domains, although it would take quite some effort.
The WAMR has offered a comprehensive framework for programming WASM applications for device and IoT usages. The framework supports running multiple applications, that are based on the event driven programming model. Here are the supporting API sets by the WAMR application framework library :
- Timer, Inter-app communication (request/response and pub/sub), Sensor, Connectivity and data transmission, 2D graphic UI
Browse the folder core/app-framework for how to extend the application framework.
Remote application management
The WAMR application manager supports remote application management from the host environment or the cloud through any physical communications such as TCP, UPD, UART, BLE, etc. Its modular design makes it able to support application management for different managed runtimes.
The tool host_tool communicates to the WAMR app manager for installing/uninstalling the WASM applications on companion chip from the host system. And the IoT App Store Demo shows the conception of remotely managing the device applications from the cloud.
Usually there are two tasks for integrating the WAMR into a particular project:
- Select what WAMR components (vmcore, libc, app-mgr, app-framework components) to be integrated, and get the associated source files added into the project building configuration
- Generate the APP SDK for developing the WASM apps on the selected libc and framework components
The WAMR SDK tools is helpful to finish the two tasks quickly. It supports menu configuration for selecting WAMR components and builds the WAMR to a SDK package that includes runtime SDK and APP SDK. The runtime SDK is used for building the native application and the APP SDK should be shipped to WASM application developers.
The WAMR samples integrate the iwasm VM core, application manager and selected application framework components.
- basic: Demonstrating how to use runtime exposed API's to call WASM functions, how to register native functions and call them, and how to call WASM function from native function.
- simple: The runtime is integrated with most of the WAMR APP libraries, and a few WASM applications are provided for testing the WAMR APP API set. It uses built-in libc and executes apps in interpreter mode by default.
- littlevgl: Demonstrating the graphic user interface application usage on WAMR. The whole LittleVGL 2D user graphic library and the UI application are built into WASM application. It uses WASI libc and executes apps in AoT mode by default.
- gui: Move the LittleVGL library into the runtime and define a WASM application interface by wrapping the littlevgl API. It uses WASI libc and executes apps in interpreter mode by default.
- multi-thread: Demonstrating how to run wasm application which creates multiple threads to execute wasm functions concurrently, and uses mutex/cond by calling pthread related API's.
- spawn-thread: Demonstrating how to execute wasm functions of the same wasm application concurrently, in threads created by host embedder or runtime, but not the wasm application itself.
- multi-module: Demonstrating the multiple modules as dependencies feature which implements the load-time dynamic linking.
- ref-types: Demonstrating how to call wasm functions with argument of externref type introduced by reference types proposal.
- wasm-c-api: Demonstrating how to run some samples from wasm-c-api proposal and showing the supported API's.
- workload: Demonstrating how to build and run some complex workloads, e.g. tensorflow-lite, XNNPACK, wasm-av1, meshoptimizer and bwa.
Project Technical Steering Committee
The WAMR PTSC Charter governs the operations of the project TSC. The current TSC members:
- lum1n0us - Liang He， email@example.com
- no1wudi Qi Huang, firstname.lastname@example.org
- qinxk-inter - Xiaokang Qin， email@example.com
- wei-tang - Wei Tang， firstname.lastname@example.org
- wenyongh - Wenyong Huang， email@example.com
- xujuntwt95329 - Jun Xu， Jun1.Xu@intel.com
- xwang98 - Xin Wang， firstname.lastname@example.org (chair)
WAMR uses the same license as LLVM: the
Apache 2.0 license with the LLVM
exception. See the LICENSE file for details. This license allows you to freely
use, modify, distribute and sell your own products based on WAMR.
Any contributions you make will be under the same license.
Check out the Wiki documents for more resources: