wasmer/lib
2019-06-03 15:31:42 -07:00
..
clif-backend Try using dependency git revision to see if it fixes CI dependency error 2019-06-01 15:29:49 -05:00
dev-utils move stdout capture from runtime core to dev-utils 2019-05-17 15:48:30 -07:00
emscripten fix bugs in em mapdir, improve it for relative paths, use it more 2019-05-29 14:20:52 -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 feature/clif-cgapi 2019-05-26 12:04:45 -05:00
middleware-common Update libraries versions to 0.4.2 2019-05-16 14:39:13 -07:00
runtime Add cache store, load, and execute test for cranelift and llvm 2019-06-01 11:35:26 -05:00
runtime-abi Merge branch 'master' into feature/clif-cgapi 2019-05-26 12:04:45 -05:00
runtime-c-api Fix clippy errors. 2019-06-03 15:31:42 -07:00
runtime-core Cargo fmt 2019-06-03 15:31:42 -07:00
singlepass-backend Merge branch 'master' into feature/clif-cgapi 2019-05-26 12:04:45 -05:00
spectests Merge branch 'master' into feature/clif-cgapi 2019-05-26 12:04:45 -05:00
wasi improve wasi envvar test 2019-05-30 12:25:14 -07:00
win-exception-handler Update libraries versions to 0.4.2 2019-05-16 14:39:13 -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