Skip to content
Standalone JIT-style runtime for WebAssembly, using Cranelift
Rust C# C C++ WebAssembly JavaScript Other
Branch: master
Clone or download
alexcrichton Simplify the `signalhandlers` module (#854)
* Remove the unused EnsureDarwinMachPorts function

When compiling the C++ shims for longjmp/setjmp/signal handling we don't
use the `USE_APPLE_MACH_PORTS` directive, so this function was entirely
unused anyway. This looks to be a holdover from when this was originally
copied from C++, but no need for keeping around this now-legacy
initialization.

* Remove the `wasmtime_init_finish` function

This looks like it's perhaps largely historical cruft at this point now
I think? The function, with the removal of the mach ports from the
previous commit, only reads the initializtion state of the signal
handlers. If the signal handlers failed to get installed, though, it
simply returns early rather than erroring out anyway. In any case a
follow-up commit will refactor `wasmtime_init_eager` to handle this as
well.

* Pare down `wasmtime_init_eager`

Similar to previous commits it looks like this function may have accrued
some debt over time, nowadays it doesn't really do much other than
capture a backtrace and install signal handlers. The `lazy_static` state
isn't really that necessary and we can rely on the `Once` primitive in
the standard library for one-time initialization.

This also updates the code to unconditionally panic if signal handlers
fail to get installed, which I think is the behavior that we'll want for
now and we can enhance it over time if necessary, but I don't think we
have a use case where it's currently necessary.
Latest commit 177af53 Jan 23, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.dependabot Update dependabot for only security updates Dec 13, 2019
.github CI: run a sample of our differential fuzz test corpus in CI Jan 18, 2020
ci Move the C API to a separate crate (#818) Jan 14, 2020
crates Simplify the `signalhandlers` module (#854) Jan 23, 2020
docs Remove the need for `HostRef<Store>` (#771) Jan 7, 2020
fuzz Merge pull request #840 from jfoote/master Jan 21, 2020
scripts Replace the global-exports mechanism with a caller-vmctx mechanism. (#… Jan 21, 2020
src Replace the global-exports mechanism with a caller-vmctx mechanism. (#… Jan 21, 2020
tests Replace the global-exports mechanism with a caller-vmctx mechanism. (#… Jan 21, 2020
.gitignore Commit Cargo.lock. (#705) Dec 13, 2019
.gitmodules Move the C API to a separate crate (#818) Jan 14, 2020
.rustfmt.toml Convert a CRLF file. Nov 9, 2019
CODE_OF_CONDUCT.md docs: Include the code of conduct directly into the mdbook Dec 3, 2019
CONTRIBUTING.md Fix links in CONTRIBUTING.md (#565) Nov 14, 2019
Cargo.lock Auto-generate the `hostcalls` module of `wasi-common` (#846) Jan 22, 2020
Cargo.toml Disable rustdoc on the wasmtime cli binary (#834) Jan 17, 2020
LICENSE Extract common interface from lucet-wasi May 4, 2019
ORG_CODE_OF_CONDUCT.md Make it a Bytecode Alliance project (#549) Nov 12, 2019
README.md Update lightbeam link (#558) Nov 13, 2019
SECURITY.md Make it a Bytecode Alliance project (#549) Nov 12, 2019
build.rs Update cranelifte and enable more SIMD spec tests (#806) Jan 11, 2020
clippy.toml General Cargo.toml cleanup. (#529) Nov 8, 2019

README.md

Wasmtime: a WebAssembly Runtime

A Bytecode Alliance project

Wasmtime is a standalone wasm-only optimizing runtime for WebAssembly and WASI. It runs WebAssembly code outside of the Web, and can be used both as a command-line utility or as a library embedded in a larger application.

To get started, visit wasmtime.dev.

build-status gitter-chat-badge minimum-rustc

There are Rust, C, and C++ toolchains that can compile programs with WASI. See the WASI intro for more information, and the WASI tutorial for a tutorial on compiling and running programs using WASI and wasmtime, as well as an overview of the filesystem sandboxing system.

Wasmtime passes the WebAssembly spec testsuite. To run it, update the tests/spec_testsuite submodule with git submodule update --remote, and it will be run as part of cargo test.

Wasmtime does not yet implement Spectre mitigations, however this is a subject of ongoing research.

Additional goals for Wasmtime include:

  • Support a variety of host APIs (not just WASI), with fast calling sequences, and develop proposals for additional API modules to be part of WASI.
  • Facilitate development and testing around the Cranelift and Lightbeam JITs, and other WebAssembly execution strategies.
  • Develop a native ABI used for compiling WebAssembly suitable for use in both JIT and AOT to native object files.

Including Wasmtime in your project

Wasmtime exposes an API for embedding as a library through the wasmtime subcrate, which contains both a high-level and safe Rust API, as well as a C-compatible API compatible with the proposed WebAssembly C API.

For more information, see the Rust API embedding chapter of the Wasmtime documentation.

It's Wasmtime.

You can’t perform that action at this time.