gnh1201/wasm-micro-runtime
1
0
Fork 0
mirror of https://github.com/bytecodealliance/wasm-micro-runtime.git synced 2026-03-14 15:48:46 +00:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
WebAssembly Micro Runtime (WAMR)
2,659 Commits 22 Branches 44 Tags 236 MiB
C 75.1%
C++ 9.6%
Python 4.9%
WebAssembly 3.7%
CMake 2.6%
Other 3.9%
9e4aa9c850
Go to file
liang.he 9e4aa9c850
fuzzing: reject non-wasm files quickly and execute aot after compilation (#4780) 
* fix: disable unsigned integer overflow sanitization in build configurations

FYI: from https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html

`-fsanitize=unsigned-integer-overflow`: Unsigned integer overflow, where the result of an unsigned integer computation cannot be represented in its type. Unlike signed integer overflow, this is not undefined behavior, but it is often unintentional. This sanitizer does not check for lossy implicit conversions performed before such a computation.

It brings a more common question: which is better, pre-additional-check or post-additional-check to fix a potential unsigned integer overflow? A pre-additional-check involves using a check to prevent integer overflow from the very beginning. A post-additional-check involves using a check after addition to see if there is an overflow.

In this project, post-additional-checking is widely used. let's follow the routine.

for performance sensitive logic, use __builtin_add_overflow etc. provide something like 9a5622791e/lib/platform.h (L176-L191) and encourage the use of them.

ref. https://github.com/bytecodealliance/wasm-micro-runtime/pull/4549#issuecomment-3218687294

* fix: update AOT compiler configuration and enhance error handling in fuzz tests
2026-03-09 18:24:43 -07:00
.devcontainer
.github build(deps): Bump github/codeql-action from 4.32.5 to 4.32.6 (#4868) 2026-03-09 18:23:27 -07:00
build-scripts fuzzing: reject non-wasm files quickly and execute aot after compilation (#4780) 2026-03-09 18:24:43 -07:00
ci Refactoring enclave sample (#4828) 2026-03-06 21:19:41 +08:00
core fuzzing: reject non-wasm files quickly and execute aot after compilation (#4780) 2026-03-09 18:24:43 -07:00
doc
gitbook Fix typo in README from WARM to WAMR (#4843) 2026-02-25 16:39:25 -08:00
language-bindings Fixed build of Go language bindings (#4825) 2026-02-06 08:56:18 +08:00
product-mini Refactoring enclave sample (#4828) 2026-03-06 21:19:41 +08:00
samples
test-tools
tests fuzzing: reject non-wasm files quickly and execute aot after compilation (#4780) 2026-03-09 18:24:43 -07:00
wamr-compiler
wamr-sdk
wamr-wasi-extensions
zephyr
.clang-format
.clang-tidy
.dockerignore
.gitignore Refactoring enclave sample (#4828) 2026-03-06 21:19:41 +08:00
ADOPTERS.md
ATTRIBUTIONS.md
CMakeLists.txt
CODE_OF_CONDUCT.md
CODEOWNERS
CONTRIBUTING.md
idf_component.yml
LICENSE
ORG_CODE_OF_CONDUCT.md
README.md
RELEASE_NOTES.md
SConscript
SECURITY.md
SUMMARY.md
TSC_Charter.md

README.md

WebAssembly Micro Runtime

A Bytecode Alliance project

Guide  Website  Chat

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 rich running modes including interpreter, Ahead-of-Time compilation(AoT) and Just-in-Time compilation (JIT). 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 which 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

Wasm post-MVP features

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

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