mirror of
https://github.com/bytecodealliance/wasm-micro-runtime.git
synced 2024-10-04 15:12:25 +00:00
WebAssembly Micro Runtime (WAMR)
aotassembly-scriptembeddedinterpreteriotjitpthreadruntimesgxwasi-nnwasi-threadswasmwasm-socketwebassembly
8318333304
At least it's sometimes useful for nuttx sim.
eg. (modified a bit to avoid github autolinks)
```
spacetanuki% lldb ./nuttx
(lldb) target create "./nuttx"
Current executable set to '/Users/yamamoto/git/nuttx/nuttx/nuttx' (x86_64).
(lldb) settings set plugin.jit-loader.gdb.enable on
(lldb) b foo
Breakpoint 1: no locations (pending).
WARNING: Unable to resolve breakpoint to any actual locations.
(lldb) r
Process 37011 launched: '/Users/yamamoto/git/nuttx/nuttx/nuttx' (x86_64)
NuttShell (NSH) NuttX-10.4.0
nsh> mount -t hostfs -o fs=/tmp/wasm /mnt
nsh> iwasm /mnt/test.aot
1 location added to breakpoint 1
Process 37011 stopped
* thread #_1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #_0: 0x0000000105800673 JIT(0x1058002d4)`foo(exenv=0x0000000101284280) at test.c:5
2
3 __attribute__((noinline))
4 void foo()
-> 5 {
6 printf("hello from %s\n", __func__);
7 }
8
Target 0: (nuttx) stopped.
(lldb) bt
* thread #_1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #_0: 0x0000000105800673 JIT(0x1058002d4)`foo(exenv=0x0000000101284280) at test.c:5
frame #_1: 0x000000010580077a JIT(0x1058002d4)`bar(exenv=0x0000000101284280) at test.c:12:2
frame #_2: 0x000000010580086a JIT(0x1058002d4)`baz(exenv=0x0000000101284280) at test.c:19:2
frame #_3: 0x0000000105800972 JIT(0x1058002d4)`__main_argc_argv(exenv=<unavailable>, argc=<unavailable>, argv=<unavailable>) at test.c:26:3
frame #_4: 0x00000001058061aa JIT(0x1058002d4)`aot_func#14 + 278
...
```
|
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| assembly-script | ||
| build-scripts | ||
| ci | ||
| core | ||
| doc | ||
| language-bindings | ||
| product-mini | ||
| samples | ||
| test-tools | ||
| tests | ||
| wamr-compiler | ||
| wamr-sdk | ||
| zephyr | ||
| .clang-format | ||
| .clang-tidy | ||
| .gitignore | ||
| ATTRIBUTIONS.md | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| ORG_CODE_OF_CONDUCT.md | ||
| README.md | ||
| RELEASE_NOTES.md | ||
| SConscript | ||
| SECURITY.md | ||
| TSC_Charter.md | ||
WebAssembly Micro Runtime
A Bytecode Alliance project
Build WAMR | Build AOT Compiler | Embed WAMR | Export Native API | Build Wasm Apps | Samples
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
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.
- Linux, Linux SGX (Intel Software Guard Extension), MacOS, Android, Windows, Windows (MinGW)
- Zephyr, AliOS-Things, VxWorks, NuttX, RT-Thread, ESP-IDF
Getting started
- Build VM core and Build wamrc AOT compiler
- Build iwasm (mini product): Linux, SGX, MacOS and Windows
- Embed into C/C++, Embed into Python, Embed into Go
- Register native APIs for Wasm applications
- Build wamrc AOT compiler
- Build Wasm applications
- Port WAMR to a new platform
- VS Code development container
- Samples and Benchmarks
Performance and memory
- Blog: The WAMR memory model
- Blog: Understand WAMR heaps and stacks
- Blog: Introduction to WAMR running modes
- Memory usage tunning: the memory model and how to tune the memory usage
- Memory usage profiling: how to profile the memory usage
- Performance tunning: 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:
- dongsheng28849455 - Dongsheng Yan, dongsheng.yan@sony.com
- loganek - Marcin Kolny, mkolny@amazon.co.uk
- lum1n0us - Liang He， liang.he@intel.com
- no1wudi Qi Huang, huangqi3@xiaomi.com
- qinxk-inter - Xiaokang Qin， xiaokang.qxk@antgroup.com
- ttrenner - Trenner, Thomas， trenner.thomas@siemens.com
- wei-tang - Wei Tang， tangwei.tang@antgroup.com
- wenyongh - Wenyong Huang， wenyong.huang@intel.com
- woodsmc - Woods, Chris， chris.woods@siemens.com
- xujuntwt95329 - Jun Xu， Jun1.Xu@intel.com
- xwang98 - Xin Wang， xin.wang@intel.com (chair)
- yamt - Takashi Yamamoto, yamamoto@midokura.com
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.