wasmer/lib
Yaron Wittenstein f73180f45e wasmer-c-api:
* adding `wasmer_import_object_new` and `wasmer_import_object_extend`
* adding test file `test-module-import-instantiate.c`
2019-08-01 14:06:25 +03:00
..
clif-backend update wasmparser and clif-fork dependencies 2019-08-01 10:13:25 +09:00
dev-utils Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
emscripten Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
emscripten-tests Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
kernel-loader Update the loader interface for 128 bit types. 2019-07-22 11:23:41 -07:00
kernel-net Remove all uses of mem::uninitialized for Rust 1.38 2019-07-31 13:21:20 +09:00
llvm-backend update wasmparser and clif-fork dependencies 2019-08-01 10:13:25 +09:00
middleware-common Fixed middleware linting 2019-07-31 21:24:46 -07:00
runtime Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
runtime-abi Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
runtime-c-api wasmer-c-api: 2019-08-01 14:06:25 +03:00
runtime-core wasmer-c-api: 2019-08-01 14:06:25 +03:00
singlepass-backend update wasmparser and clif-fork dependencies 2019-08-01 10:13:25 +09:00
spectests Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
wasi Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
wasi-tests Updated version to 0.6.0 2019-07-31 10:28:45 -07:00
win-exception-handler Updated version to 0.6.0 2019-07-31 10:28:45 -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