807: Implement Send for Instance r=MarkMcCaskey a=MarkMcCaskey # Review - [x] Create a short description of the the change in the CHANGELOG.md file Resolves #748 WIP ## List of changes ### Commit 1 - `Global`s use Arc instead of RC - Export `Context` and `FuncPointer` manually implement Send - `ImportObject` uses `Arc<Mutex<HashMap<...>>>` Instead of `Rc<RefCell<HashMap<...>>>`; removed `get_namespace` method in favor of continuation style to deal with locking the Mutex - `Func` manually implements `Send` (TODO: this change needs to be checked in depth) ### Commit 2 - `unsafe impl Send for Export {}` (temporary to allow Memory to be not Send) - RefCell -> Mutex in Global and Table - Rc -> Arc in Table - Namespace's `IsExport`s must be `Send` (Done to avoid touching much more of the code (i.e. `trait IsExport: Send` requires a lot -- maybe this is what we should do though) - Make `Host` and `Wasm` `Func`s Send (manual implementation) - Manual implementation for `LocalTable` and `AnyFunc` ### Commit 3 - rm placeholder `unsafe impl Send for Export {}` - Manual implementation for `LocalBacking` and `ImportBacking` (both seemed to be not Send due to direct ownership of mutable pointers in their containers) - ImportObject's state creator Fn trait object is now ` + Send + Sync + 'static` (required because it's in an Arc) - Manually implement Send for `InstanceInner` because it holds a raw pointer, `LocalBacking` and `ImportBacking` are marked Send separately - Memory: All Rc -> Arc (including unshared memory); All RefCell -> Mutex (including unshared memory) - Manual implementation of Send and Sync on `UnsharedMemoryInternal` - Manual implementation of Send and Sync on `SharedMemoryInternal` - Change `runtime-core::unix::memory::Memory.fd` from `Option<Rc<Rawfd>>` to `Option<Arc<Rawfd>>` (not strictly required for this change because Memory has manual implementations of Send and Sync, but Arc seems more correct here and there's no comment justifying the use of Rc) - Manual implementation of Send for `ImportedFunc` Co-authored-by: Mark McCaskey <mark@wasmer.io> Co-authored-by: Mark McCaskey <markmccaskey@users.noreply.github.com>
Introduction
Wasmer is a standalone WebAssembly runtime, for running WebAssembly outside of the Browser, supporting WASI and Emscripten.
Install the Wasmer CLI with:
curl https://get.wasmer.io -sSfL | sh
Note: Wasmer is also available on Windows
Languages
Wasmer runtime can be used as a library embedded in different languages, so you can use WebAssembly anywhere:
Language | Author(s) | Maintenance | Release | Stars | |
---|---|---|---|---|---|
Rust | Wasmer | actively developed | |||
C/C++ | Wasmer | actively developed | |||
Python | Wasmer | actively developed | |||
Go | Wasmer | actively developed | |||
PHP | Wasmer | actively developed | |||
Ruby | Wasmer | actively developed | |||
Postgres | Wasmer | actively developed | |||
C#/.Net | Miguel de Icaza | actively developed | |||
R | Dirk Schumacher | actively developed | |||
Swift | Mark Malström | passively maintened | |||
❓ | your language is missing? |
Usage
Wasmer can execute both the standard binary format (.wasm
) and the text
format defined by the WebAssembly reference interpreter (.wat
).
Once installed, you will be able to run any WebAssembly files (including Lua, PHP, SQLite and nginx!):
# Run Lua
wasmer run examples/lua.wasm
You can find more wasm/wat
examples in the examples directory.
With WAPM
Installing Wasmer through wasmer.io
includes
wapm
, the WebAssembly Package Manager.
Wapm allows you to easily download, run, and distribute WebAssembly binaries.
# Install cowsay globally
wapm install -g cowsay
# Run cowsay
wapm run cowsay "Hello, world!"
For more information about wapm, check out the website and this example program.
Code Structure
Wasmer is structured into different directories:
src
: code related to the Wasmer executable itselflib
: modularized libraries that Wasmer uses under the hoodexamples
: some useful examples to getting started with Wasmer
Dependencies
Building Wasmer requires rustup.
To build Wasmer on Windows, download and run rustup-init.exe
then follow the onscreen instructions.
To build on other systems, run:
curl https://sh.rustup.rs -sSf | sh
Other dependencies
Please select your operating system:
macOS
macOS
If you have Homebrew installed:
brew install cmake
Or, in case you have MacPorts:
sudo port install cmake
Debian-based Linuxes
Debian-based Linuxes
sudo apt install cmake pkg-config libssl-dev
FreeBSD
FreeBSD
pkg install cmake
Windows
Windows (MSVC)
Windows support is experimental. WASI is fully supported, but Emscripten support is on the works (this means nginx and Lua do not work on Windows - you can track the progress on this issue).
-
Install Visual Studio
-
Install Rust for Windows
-
Install Python for Windows. The Windows x86-64 MSI installer is fine. Make sure to enable "Add python.exe to Path" during installation.
-
Install Git for Windows. Allow it to add
git.exe
to your PATH (default settings for the installer are fine). -
Install CMake. Ensure CMake is in your PATH.
-
Install LLVM 8.0
Building
Wasmer is built with Cargo, the Rust package manager.
The Singlepass backend requires nightly, so if you want to use it,
Set Rust Nightly:
rustup default nightly
Otherwise an up to date (see badge above) verison of stable Rust will work.
And install Wasmer
# checkout code
git clone https://github.com/wasmerio/wasmer.git
cd wasmer
# install tools
make release-clif # To build with cranelift (default)
make release-llvm # To build with llvm support
make release-singlepass # To build with singlepass support
# or
make release # To build with singlepass, cranelift and llvm support
Testing
Thanks to spec tests we can ensure 100% compatibility with the WebAssembly spec test suite.
You can run all the tests with:
rustup default nightly
make test
Testing backends
Each backend can be tested separately:
- Singlepass:
make singlepass
- Cranelift:
make cranelift
- LLVM:
make llvm
Testing integrations
Each integration can be tested separately:
- Spec tests:
make spectests
- Emscripten:
make emtests
- WASI:
make wasi
- Middleware:
make middleware
- C API:
make capi
Benchmarking
Benchmarks can be run with:
make bench-[backend]
# for example
make bench-singlepass
Roadmap
Wasmer is an open project guided by strong principles, aiming to be modular, flexible and fast. It is open to the community to help set its direction.
Below are some of the goals of this project (in order of priority):
- It should be 100% compatible with the WebAssembly spec tests
- It should be fast (partially achieved)
- Support WASI - released in 0.3.0
- Support Emscripten calls (in the works)
- Support Go js ABI calls
Architecture
If you would like to know how Wasmer works under the hood, please see docs/architecture.md.
License
Wasmer is primarily distributed under the terms of the MIT license (LICENSE).