Skip to content
/ wasm3 Public
forked from wasm3/wasm3

πŸš€ The fastest WebAssembly interpreter, and the most universal runtime

License

Notifications You must be signed in to change notification settings

skrphv/wasm3

Β 
Β 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

SWUbanner

Wasm3

WAPM GitHub issues Tests status Fuzzing Status GitHub license

A fast WebAssembly interpreter and the most universal WASM runtime.
Based on CoreMark 1.0 and independent benchmarks. Your mileage may vary.

Twitter Discord Telegram

Getting Started

Here's a small getting started guide. Click here to start:

LIVE DEMO

Installation

Please follow the installation instructions.

Wasm3 can also be used as a library for:

Python3 β”‚ Rust β”‚ C/C++ β”‚ GoLang β”‚ Zig β”‚ Perl
Swift β”‚ .Net β”‚ Nim β”‚ Arduino, PlatformIO, Particle β”‚ QuickJS

Status

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 execute wasm3 (self-hosting)

Features

Webassembly Core 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)
☐ Multiple memories
☐ Reference types
☐ Tail call optimization
☐ Fixed-width SIMD
☐ Exception handling

Motivation

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 many 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 actually 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.

Used by

γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€ γ€€

Further Resources

Demos
Installation instructions
Cookbook
Troubleshooting
Build and Development instructions
Supported Hardware
Testing & Fuzzing
Performance
Interpreter Architecture
Logging
Awesome WebAssembly Tools

License

This project is released under The MIT License (MIT)

About

πŸš€ The fastest WebAssembly interpreter, and the most universal runtime

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 90.5%
  • C++ 3.7%
  • Python 2.8%
  • CMake 1.0%
  • Makefile 0.7%
  • Shell 0.4%
  • Other 0.9%