wasmer/lib
Nick Lewycky 0ed104b543 Remove incorrect comment -- wasmer does support mutable globals.
The reason this test needed to be disabled is correctly documented in the comment above.
2019-07-23 17:13:02 -07:00
..
clif-backend Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
dev-utils Prepare for release of 0.5.7 2019-07-23 11:20:59 -07:00
emscripten Prepare for release of 0.5.7 2019-07-23 11:20:59 -07:00
emscripten-tests Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
kernel-loader Update the loader interface for 128 bit types. 2019-07-22 11:23:41 -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 simd 2019-07-23 13:51:15 -07:00
middleware-common Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
runtime Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
runtime-abi Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
runtime-c-api Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
runtime-core Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
singlepass-backend Merge branch 'master' into simd 2019-07-23 13:51:15 -07:00
spectests Remove incorrect comment -- wasmer does support mutable globals. 2019-07-23 17:13:02 -07:00
wasi Prepare for release of 0.5.7 2019-07-23 11:20:59 -07:00
wasi-tests Prepare for release of 0.5.7 2019-07-23 11:20:59 -07:00
win-exception-handler Prepare for release of 0.5.7 2019-07-23 11:20:59 -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