wazero

Files

Crypt Keeper d04199d1c3 cli,wasi: passes mounts directly as preopens to run rust wasi-testsuite (#1078 )

This allows wasi to see mounts as individual preopens instead of
virtualized under a root. (GOOS=js doesn't use pre-opens so it still
sees a virtual root). This allows us to progress wasi-testsuite rust
tests, but acknowledges a current glitch in zig support, which is
tracked separately as #1077

Signed-off-by: Adrian Cole <adrian@tetrate.io>

2023-01-30 08:11:16 +02:00

assemblyscript

logging: adds exit scope and fixes mtim bug (#1074 )

2023-01-29 08:43:14 +02:00

emscripten

logging: adds memory scope (#1076 )

2023-01-29 10:58:59 +02:00

Deletes namespace API (#1018 )

2023-01-10 14:11:46 +09:00

wasi_snapshot_preview1

cli,wasi: passes mounts directly as preopens to run rust wasi-testsuite (#1078 )

2023-01-30 08:11:16 +02:00

README.md

Stops using "ex." to abbreviate "for example" (#827 )

2022-10-24 11:51:48 +09:00

README.md

wazero imports

Packages in this directory implement the host imports needed for specific languages or shared compiler toolchains.

AssemblyScript e.g. asc X.ts --debug -b none -o X.wasm
Emscripten e.g. em++ ... -s STANDALONE_WASM -o X.wasm X.cc
Go e.g. GOARCH=wasm GOOS=js go build -o X.wasm X.go
WASI e.g. tinygo build -o X.wasm -target=wasi X.go

Note: You may not see a language listed here because it either works without host imports, or it uses WASI. Refer to https://wazero.io/languages/ for more.

Please open an issue if you would like to see support for another compiled language or toolchain.

Overview

WebAssembly has a virtual machine architecture where the host is the process embedding wazero and the guest is a program compiled into the WebAssembly Binary Format, also known as Wasm (%.wasm).

The only features that work by default are computational in nature, and the only way to communicate is via functions, memory or global variables.

When a compiler targets Wasm, it often needs to import functions from the host to satisfy system calls needed for functionality like printing to the console, getting the time, or generating random values. The technical term for this bridge is Application Binary Interface (ABI), but we'll call them simply host imports.

Packages in this directory are sometimes well re-used, such as the case in WASI. For example, Rust, TinyGo, and Zig can all target WebAssembly in a way that imports the same "wasi_snapshot_preview1" module in the compiled %.wasm file. To support any of these, wazero users can invoke wasi_snapshot_preview1.Instantiate on their wazero.Runtime.

Other times, host imports are either completely compiler-specific, such as the case with GOARCH=wasm GOOS=js, or coexist alongside WASI, such as the case with Emscripten.