wasmer/lib
Ivan Enderlin 4c2fb953a4 feat(interface-types) InterfaceValue::Record now takes a Vec1.
It matches the definition of `InterfaceType::Record`.
2020-04-09 12:10:48 +02:00
..
api Improve consistency of names, reuse more code, and reorganize a bit 2020-03-31 16:00:52 -07:00
clif-backend Minor code update, move conditional block inwards 2020-03-24 16:00:32 -07:00
dev-utils Move emscripten-tests to tests dir + misc fixes 2020-04-02 16:51:58 -07:00
emscripten Fix up tests for CI 2020-04-06 11:42:44 -07:00
interface-types feat(interface-types) InterfaceValue::Record now takes a Vec1. 2020-04-09 12:10:48 +02:00
kernel-loader Fix kernel-loader with musl. 2020-01-29 01:07:23 +08:00
kernel-net Add MIT license to crates that were missing it 2019-12-22 12:28:33 +01:00
llvm-backend Use the inkwell package on crates.io!! 2020-03-27 15:47:50 -07:00
middleware-common Prepare for 0.16.2 release 2020-03-11 19:15:31 -07:00
runtime Convert usages of Instance::{func,dyn_func} to exports.get 2020-03-26 18:13:45 -07:00
runtime-c-api chore(runtime-c-api) Update C/C++ headers. 2020-03-26 07:32:57 +01:00
runtime-core Merge #1350 2020-04-02 15:11:41 +00:00
singlepass-backend Merge branch 'master' into android 2020-03-23 13:29:18 -07:00
wasi Support Android 2020-03-23 11:55:31 +09:00
wasi-experimental-io-devices Prepare for 0.16.2 release 2020-03-11 19:15:31 -07:00
win-exception-handler Fix warning (from clang) 2020-03-18 20:07:12 +01:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Added link to a custom ABI example repo 2020-02-16 12:48:20 -08: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:

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