wasmer/lib
2019-07-16 13:50:56 -07:00
..
clif-backend Update to nix 0.14. 2019-07-11 12:28:56 +02:00
dev-utils update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
emscripten update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
emscripten-tests update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
kernel-loader Renamed kwasm-net to wasmer-kernel-net 2019-05-15 10:34:56 -07:00
kernel-net Rename wasmer-kernel-net to kernel-net. 2019-05-16 09:22:40 +08:00
llvm-backend Merge branch 'master' into nlewycky/llvm 2019-07-11 16:48:46 -07:00
middleware-common update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-abi update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-c-api update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-core Merge remote-tracking branch 'origin/master' into feature/wasi-readlink 2019-07-16 13:50:56 -07:00
singlepass-backend Update loader-kernel feature name, fix compilation track state, cargo fmt 2019-07-12 23:02:57 -05:00
spectests update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
wasi Merge remote-tracking branch 'origin/master' into feature/wasi-readlink 2019-07-16 13:50:56 -07:00
wasi-tests Merge remote-tracking branch 'origin/master' into feature/wasi-readlink 2019-07-16 13:50:56 -07:00
win-exception-handler update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Renamed dynasm backend to singlepass 2019-04-11 12:44:03 -07:00

Wasmer Libraries

Wasmer is modularized into different libraries, separated into three main sections:

Runtime

The core of Wasmer is the runtime, which provides the necessary abstractions to create a good user experience when embedding.

The runtime is divided into two main libraries:

  • runtime-core: The main implementation of the runtime.
  • runtime: Easy-to-use API on top of runtime-core.

Integrations

The integration builds on the Wasmer runtime and allow us to run WebAssembly files compiled for different environments.

Wasmer intends to support different integrations:

  • WASI: run WebAssembly files with the WASI ABI.
  • Emscripten: run Emscripten-generated WebAssembly files, such as Lua or nginx.
  • Go ABI: we will work on this soon! Want to give us a hand?
  • Blazor: research period, see tracking issue

Backends

The Wasmer runtime is designed to support multiple compiler backends, allowing the user to tune the codegen properties (compile speed, performance, etc) to best fit their use case.

Currently, we support multiple backends for compiling WebAssembly to machine code:

  • singlepass-backend: Single pass backend - super fast compilation, slower runtime speed
  • clif-backend: Cranelift backend - slower compilation, normal runtime speed
  • llvm-backend: LLVM backend - slow compilation, native runtime speed