wasmer/lib
2019-07-10 14:43:54 -07:00
..
clif-backend Add V128 to wasmer runtime. Unimplemented in clif-backend. Other backends don't build. 2019-07-10 13:48:12 -07:00
dev-utils update to version 0.5.4 2019-07-05 13:35:55 -07:00
emscripten fix emscripten tests 2019-07-09 13:41:40 -07:00
emscripten-tests fix emscripten tests 2019-07-09 13:41:40 -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 Reformat. 2019-07-10 14:28:07 -07:00
middleware-common Update wabt to 0.8 release. 2019-07-10 13:48:12 -07:00
runtime Update wabt to 0.8 release. 2019-07-10 13:48:12 -07:00
runtime-abi update to version 0.5.4 2019-07-05 13:35:55 -07:00
runtime-c-api Stub out support for V128 in the C API for now. 2019-07-10 13:54:36 -07:00
runtime-core Add V128 to wasmer runtime. Unimplemented in clif-backend. Other backends don't build. 2019-07-10 13:48:12 -07:00
singlepass-backend Add V128 stubs to allow singlepass backend to build again. 2019-07-10 13:48:12 -07:00
spectests Added simd spectest file 2019-07-10 14:43:54 -07:00
wasi fix abi crates depending on compilers 2019-07-09 11:58:03 -07:00
wasi-tests fix emscripten dependencies by making separate test crate 2019-07-09 12:07:05 -07:00
win-exception-handler update to version 0.5.4 2019-07-05 13:35:55 -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