wasmer/lib
2019-05-06 18:02:39 -07:00
..
clif-backend update version number to 0.4.1 2019-05-06 18:02:39 -07:00
emscripten update version number to 0.4.1 2019-05-06 18:02:39 -07:00
llvm-backend update version number to 0.4.1 2019-05-06 18:02:39 -07:00
middleware-common update version number to 0.4.1 2019-05-06 18:02:39 -07:00
runtime update version number to 0.4.1 2019-05-06 18:02:39 -07:00
runtime-abi update version number to 0.4.1 2019-05-06 18:02:39 -07:00
runtime-c-api update version number to 0.4.1 2019-05-06 18:02:39 -07:00
runtime-core update version number to 0.4.1 2019-05-06 18:02:39 -07:00
singlepass-backend update version number to 0.4.1 2019-05-06 18:02:39 -07:00
spectests update version number to 0.4.1 2019-05-06 18:02:39 -07:00
wasi update version number to 0.4.1 2019-05-06 18:02:39 -07:00
win-exception-handler update version number to 0.4.1 2019-05-06 18:02:39 -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