wasmer/lib
Nick Lewycky 481bdb7d48 Implement saturation part of the saturating truncation operators.
These are described here: https://github.com/WebAssembly/nontrapping-float-to-int-conversions/blob/master/proposals/nontrapping-float-to-int-conversion/Overview.md
with the relevant text being:
"Instead of trapping on positive or negative overflow, they return the maximum or minimum integer value, respectively, and do not trap. (This behavior is also referred to as 'saturating'.)"
"Instead of trapping on NaN, they return 0 and do not trap."
2019-07-11 17:55:40 -07:00
..
clif-backend Merge branch 'master' into release-0.5.5 2019-07-10 16:35:00 -07:00
dev-utils update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
emscripten update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
emscripten-tests update version numbers to 0.5.5 2019-07-09 17:43:04 -07: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 Implement saturation part of the saturating truncation operators. 2019-07-11 17:55:40 -07:00
middleware-common update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-abi update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-c-api update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
runtime-core remove colons from feature names 2019-07-09 17:57:31 -07:00
singlepass-backend update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
spectests update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
wasi update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
wasi-tests update version numbers to 0.5.5 2019-07-09 17:43:04 -07:00
win-exception-handler update version numbers to 0.5.5 2019-07-09 17:43:04 -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

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