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
31cc4b7662
wasmer/lib
History
Mark McCaskey cd9ef3c49a fix bugs and clean up path logic
2019-03-19 11:31:45 -07:00
..
clif-backend fix lots of warnings 2019-03-15 14:10:17 -07:00
emscripten fix lots of warnings 2019-03-15 14:10:17 -07:00
llvm-backend Use wasmerio fork of inkwell 2019-03-11 10:03:40 -07:00
runtime fix bugs and clean up path logic 2019-03-19 11:31:45 -07:00
runtime-c-api feat(runtime-c-api) wasmer_validate expects a *const uint8_t. 2019-03-14 12:33:40 +01:00
runtime-core change output to go to OUT_DIR 2019-03-19 11:23:04 -07:00
spectests create an llvm flag 2019-03-11 09:58:09 -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 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: