fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 22:25:40 +00:00
Code Issues Projects Releases Wiki Activity
93a6279833
wasmer/lib
History
Mackenzie Clark 12b53a48ad fix tests
2019-03-24 17:54:52 -07:00
..
clif-backend Merge branch 'master' into feature/vfs 2019-03-16 13:38:02 -07:00
dynasm-backend lint 2019-03-24 17:35:37 -07:00
emscripten get it building with zbox fork 2019-03-24 16:38:45 -07:00
llvm-backend reset a cargo manifests 2019-03-12 13:58:33 -07:00
runtime Merge remote-tracking branch 'origin/master' into feature/dynasm-backend 2019-03-20 19:54:29 +08:00
runtime-abi fix tests 2019-03-24 17:54:52 -07:00
runtime-c-api Merge branch 'master' into feat-runtime-c-api-cache 2019-03-19 16:35:32 +01:00
runtime-core Merge branch 'master' 2019-03-23 00:27:55 -07:00
spectests Fix dependencies. 2019-03-18 16:14:11 +08:00
win-exception-handler fix lots of warnings 2019-03-15 14:10:17 -07:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Added dynasm-backend to the libraries README 2019-03-21 21:12:01 -07:00

README.md

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:

  • 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:

  • dynasm-backend: Dynasm 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