fluencelabs/wasmer
1
0
Fork 0
mirror of https://github.com/fluencelabs/wasmer synced 2024-12-13 22:25:40 +00:00
Code Issues Projects Releases Wiki Activity
d3c75a38fa
wasmer/lib
History
Ivan Enderlin d3c75a38fa fix(runtime-c-api) wasmer_instance_call types matches wasmer_export_func_*_arity. 
The `wasmer_export_func_params_arity` and
`wasmer_export_func_returns_arity` functions store the arity in a
`uint32_t`. The `wasmer_instance_call` expects `c_int`. There is a
type mismatch here. It's not annoying in C or C++, but in some other
languages that have bindings to C/C++, it can imply useless casting.

This patch changes `wasmer_instance_call` to expect `uint32_t` for
`params_len` and `results_len` to match the
`wasmer_export_func_*_arity` functions.
2019-05-14 11:46:43 +02:00
..
clif-backend Improved docs and fixed few typos 2019-05-13 11:18:57 -07:00
emscripten Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
llvm-backend Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
middleware-common Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
runtime Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
runtime-abi Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
runtime-c-api fix(runtime-c-api) wasmer_instance_call types matches wasmer_export_func_*_arity. 2019-05-14 11:46:43 +02:00
runtime-core Improved docs and fixed few typos 2019-05-13 11:18:57 -07:00
singlepass-backend Improved docs and fixed few typos 2019-05-13 11:18:57 -07:00
spectests update version number to 0.4.1 2019-05-06 18:02:39 -07:00
wasi Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -05:00
win-exception-handler Add deny for unreachable patterns and unused unsafe 2019-05-12 00:33:02 -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