fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 14:25:32 +00:00
Code Issues Projects Releases Wiki Activity
b5697d854a
wasmer/lib
History
Mackenzie Clark b5697d854a fix typos in vfs tests
2019-03-12 12:01:45 -07:00
..
clif-backend parse and store custom sections from wasm, guarded by vfs feature flag 2019-03-12 10:45:44 -07:00
emscripten add the feature flag for llvm backend 2019-03-12 11:59:50 -07:00
llvm-backend add the feature flag for llvm backend 2019-03-12 11:59:50 -07:00
runtime Fixed default compiler on windows 2019-03-07 19:11:29 -08:00
runtime-abi fix typos in vfs tests 2019-03-12 12:01:45 -07:00
runtime-c-api Merge branch 'master' into feat-runtime-c-api-instance-context-data 2019-03-12 09:02:05 +01:00
runtime-core parse and store custom sections from wasm, guarded by vfs feature flag 2019-03-12 10:45:44 -07:00
spectests Only use llvm in non windows envs 2019-03-07 18:26:29 -08:00
win-exception-handler fix appveyor installer and build (#224) 2019-03-01 13:16:32 -08:00
.gitignore Remove generated spectest codes from repo. 2019-01-12 23:48:21 -05:00
README.md Update README.md 2019-03-07 20:39:58 -08: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: