fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 06:15:33 +00:00
Code Issues Projects Releases Wiki Activity
21dd01c3aa
wasmer/lib
History
losfair 21dd01c3aa Fix LLVM backend compilation and segfaults.
2019-04-30 15:52:43 +08:00
..
clif-backend Merge branch 'master' into feature/cleanup-imports-unsafe 2019-04-24 08:37:06 -07:00
emscripten Return type normalization, and change return errors from imported functions 2019-04-22 11:42:52 -07:00
llvm-backend Fix LLVM backend compilation and segfaults. 2019-04-30 15:52:43 +08:00
middleware-common Cargo fmt 2019-04-28 12:54:45 +08:00
runtime Add error propagation test 2019-04-22 15:53:21 -07:00
runtime-abi update crate version numbers to 0.3.0 2019-04-12 12:19:46 -07:00
runtime-c-api update crate version numbers to 0.3.0 2019-04-12 12:19:46 -07:00
runtime-core Fix incomplete data section 2019-04-28 15:38:18 +08:00
singlepass-backend Add missing .rev() on parameter list and simulate "red zone". 2019-04-28 13:31:22 +08:00
spectests Add initial progress to add LLVM to module refactor 2019-04-29 00:13:34 -05:00
wasi Fix debug issue 2019-04-26 17:40:55 -07:00
win-exception-handler Cleanup build warnings imports and unnecessary unsafe 2019-04-20 20:37:39 -05: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

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:

  • 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