WebAssembly Micro Runtime

A Bytecode Alliance project

Guide Website Chat

WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime with small footprint, high performance and highly configurable features for applications cross from embedded, IoT, edge to Trusted Execution Environment (TEE), smart contract, cloud native and so on. It includes a few parts as below:

VMcore: A set of runtime libraries for loading and running Wasm modules. It supports several execution modes including interpreter, Ahead-of-Time compilation(AoT) and Just-in-Time compilation (JIT). The WAMR supports two JIT tiers - Fast JIT, LLVM JIT, and dynamic tier-up from Fast JIT to LLVM JIT.
iwasm: The executable binary built with WAMR VMcore supports WASI and command line interface.
wamrc: The AOT compiler to compile Wasm file into AOT file
Useful components and tools for building real solutions with WAMR vmcore:
- App-framework: A framework for supporting APIs for the Wasm applications
- App-manager: a framework for dynamical loading the Wasm module remotely
- WAMR-IDE: An experimental VSCode extension for developping WebAssembly applications with C/C++

Key features

Full 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 and JIT
Self-implemented AOT module loader to enable AOT working on Linux, Windows, MacOS, Android, SGX and MCU systems
Choices of Wasm application libc support: the built-in libc subset for the embedded environment or WASI for the standard libc
The simple C APIs to embed WAMR into host environment, see how to integrate WAMR and the API list
The mechanism to export native APIs to Wasm applications, see how to register native APIs
Multiple modules as dependencies, ref to document and sample
Multi-thread, pthread APIs and thread management, ref to document and sample
wasi-threads, ref to document and sample
Linux SGX (Intel Software Guard Extension) support, ref to document
Source debugging support, ref to document
XIP (Execution In Place) support, ref to document
Berkeley/Posix Socket support, ref to document and sample
Multi-tier JIT and Running mode control
Language bindings: Go, Python, Rust

Wasm post-MVP features

wasm-c-api, ref to document and sample
128-bit SIMD, ref to samples/workload
Reference Types, ref to document and sample
Non-trapping float-to-int conversions
Sign-extension operators, Bulk memory operations
Multi-value, Tail-call, Shared memory

Supported architectures and platforms

The WAMR VMcore 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)
XTENSA, MIPS, ARC

The following platforms are supported, click each link below for how to build iwasm on that platform. Refer to WAMR porting guide for how to port WAMR to a new platform.

Getting started

Performance and memory

Blog: The WAMR memory model
Blog: Understand WAMR heaps and stacks
Blog: Introduction to WAMR running modes
Memory usage tuning: the memory model and how to tune the memory usage
Memory usage profiling: how to profile the memory usage
Performance tuning: how to tune the performance
Benchmarks: checkout these links for how to run the benchmarks: PolyBench, CoreMark, Sightglass, JetStream2
Performance and footprint data: the performance and footprint data

Project Technical Steering Committee

The WAMR PTSC Charter governs the operations of the project TSC. The current TSC members:

License

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.

More resources

License

Poohl/wasm-micro-runtime

ErrorLooks like something went wrong!

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages