fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-12 22:05:33 +00:00
Code Issues Projects Releases Wiki Activity
95f39cedec
wasmer/lib
History
Syrus 95f39cedec Fixed last linting issues 
(hopefully)
2019-06-14 09:53:07 +02:00
..
clif-backend Merge branch 'master' into feature/metering 2019-06-02 09:31:34 -05:00
dev-utils move stdout capture from runtime core to dev-utils 2019-05-17 15:48:30 -07:00
emscripten Fixed last linting issues 2019-06-14 09:53:07 +02: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 Fix ctx layout in LLVM. 2019-06-05 02:13:10 +08:00
middleware-common Add black_box to benchmarking 2019-06-06 23:30:31 -05:00
runtime Add MiddlewareChain and StreamingCompiler to runtime 2019-06-09 23:24:10 -05:00
runtime-abi Metering for LLVM. 2019-05-31 15:36:08 +08:00
runtime-c-api Naming fixes and documentation for trampoline API. 2019-06-05 01:38:35 +08:00
runtime-core remove duplicated code, wrap WasmPtr on wasi side 2019-06-11 11:10:42 +02:00
singlepass-backend Fix typo in machine. 2019-06-08 22:56:13 +08:00
spectests Merge branch 'master' into feature/clif-cgapi 2019-05-26 12:04:45 -05:00
wasi remove duplicated code, wrap WasmPtr on wasi side 2019-06-11 11:10:42 +02:00
win-exception-handler Update libraries versions to 0.4.2 2019-05-16 14:39:13 -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

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