wasmer/lib
Nick Lewycky 05816e3221 This is no longer referring to the correct line.
It's supposed to be 352 which is already there.
2019-09-16 13:13:21 -07:00
..
clif-backend Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
dev-utils Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
emscripten Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
emscripten-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
kernel-loader Improved docs with custom logo and favicon 2019-09-03 17:06:31 -07:00
kernel-net Improved docs with custom logo and favicon 2019-09-03 17:06:31 -07:00
llvm-backend Switch from PIC+Default (small) to Static+Large. Should fix flaky test failures. 2019-09-16 10:49:39 -07:00
middleware-common Add required-by-cargo version pinning in manifest for middleware-common 2019-09-12 12:51:39 -07:00
middleware-common-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-abi Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-c-api Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
runtime-core Bump indexmap from 1.1.0 to 1.2.0 2019-09-12 20:39:52 +00:00
singlepass-backend fix CodeGen message type 2019-09-16 11:00:03 +02:00
spectests This is no longer referring to the correct line. 2019-09-16 13:13:21 -07:00
wasi Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
wasi-tests Prepare for 0.7.0 release 2019-09-12 12:44:38 -07:00
win-exception-handler Prepare for 0.7.0 release 2019-09-12 12:44:38 -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