fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-14 06:35:40 +00:00
Code Issues Projects Releases Wiki Activity
39ccf403f3
wasmer/lib
History
Lachlan Sneff d9b89b46ee Fix bug in deref of WasmPtr<T, Array>
2019-03-28 22:22:46 -07:00
..
clif-backend clean up implementation 2019-03-27 14:01:27 -07:00
dynasm-backend fix lint errors 2019-03-27 14:30:57 -07:00
emscripten make string multi-line 2019-03-27 08:36:53 -07:00
llvm-backend add small fix 2019-03-28 10:08:41 -07:00
runtime clean up (second pass) 2019-03-27 14:08:17 -07:00
runtime-c-api fix lint errors 2019-03-27 14:30:57 -07:00
runtime-core Add helper types and half-ish of the wasi signatures 2019-03-28 17:00:10 -07:00
spectests Fix dependencies. 2019-03-18 16:14:11 +08:00
wasi Fix bug in deref of WasmPtr<T, Array> 2019-03-28 22:22:46 -07: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