fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-15 15:15:40 +00:00
Code Issues Projects Releases Wiki Activity
80b809383e
wasmer/lib
History
Mark McCaskey 50a22bcae2 implement emscripten resize_heap
2019-04-08 16:17:34 -07:00
..
clif-backend Merge #321 2019-04-04 17:10:51 +00:00
dynasm-backend doc(lib) Add basic README.md. 2019-03-29 10:17:24 +01:00
emscripten implement emscripten resize_heap 2019-04-08 16:17:34 -07:00
llvm-backend Merge #310 2019-04-01 10:18:56 +00:00
runtime Add Export and GlobalDescriptor to Runtime API 2019-04-02 22:10:49 -05:00
runtime-abi lint 2019-03-28 13:01:02 -07:00
runtime-c-api fix(runtime-c-api) Remove last warnings. 2019-03-29 15:56:08 +01:00
runtime-core implement emscripten resize_heap 2019-04-08 16:17:34 -07:00
spectests doc(lib) Add basic README.md. 2019-03-29 10:17:24 +01:00
wasi Fix format 2019-04-05 23:55:04 -07:00
win-exception-handler doc(lib) Add basic README.md. 2019-03-29 10:17:24 +01: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