Files
wasm2go/testdata/vtable_dispatch.wat
bd85549918 wasm2go: a WebAssembly-to-Go ahead-of-time transpiler (#1)
* wasm2go: a WebAssembly-to-Go ahead-of-time transpiler

wasm2go translates a WebAssembly binary into standalone Go source. The
generated package runs the module natively — no interpreter and no
embedded wasm runtime — so it builds and links like ordinary Go code.
This makes it practical to ship a wasm-compiled library (for example a
large C/C++ codebase built with the WASI SDK) inside a Go program
without the startup and memory cost of a wasm engine.

Components:

- internal/wasm — the WebAssembly binary parser.
- internal/codegen — translates a parsed module into Go source through
  the SSA lowering + optimization + emission pipeline.
- internal/ssa — a lightweight SSA IR plus optimization passes
  (const-propagation, DCE, CSE, branch folding, memory promotion).
- transpile — the public library API: Parse, Translate, and the
  Transpile one-shot convenience wrapper.
- cmd/wasm2go — the command-line interface.
- internal/testfixture — shared helper that compiles testdata/*.wat
  to wasm on demand via wat2wasm.

Library API (Options):

- Required: Package, OutputImportPath.
- Optional: BulkExportPrefix (per-export Inv_<svc>_<mt> dispatch for
  modules with uniformly-named exports), EntryExports (narrow DCE
  root set), KeepDeadFuncs (disable DCE for diff/debug),
  PromotionReportPath (write SSA memory-promotion JSON).

Everything else is auto-derived from the input: the SSA pipeline runs
unconditionally; data segments emit as //go:embed sidecars; wasi
imports translate to Go-native syscalls; modules whose total
function-body bytes exceed an internal threshold are emitted as a
chain of //go:linkname-split sub-packages so the Go compiler stays
inside a bounded per-package memory budget.

WASI runtime: full wasi_snapshot_preview1 coverage. Args/environ,
clocks, fd_*, path_* (open/create_directory/unlink_file/
remove_directory/rename/filestat_get/filestat_set_times/link/
symlink/readlink), readdir, pread/pwrite, sync/datasync, poll_oneoff
(clock + fd-event branches), sched_yield, random_get, proc_exit,
proc_raise, sock_accept/recv/send/shutdown — every call routes to the
Go stdlib or golang.org/x/sys/unix equivalent. Per-platform companion
files (unix/linux/darwin/windows) carry the bits that differ across
OSes; the translated module is a normal Go program with the host's
ordinary filesystem and network reach.

Release engineering for the public repository:

- GitHub Actions CI: build, vet, race-enabled tests behind an 85%
  coverage gate, golangci-lint — all driven through make targets.
- Release workflow runs GoReleaser on version tags, including
  deb/rpm/apk packages, with build-provenance attestations recorded
  for every release asset.
- A release-test workflow runs `make release/check` (GoReleaser
  config validation + a publish-free dry-run build) on every PR and
  main push so a broken release is caught before tag time.
- golangci-lint and goreleaser are pinned in tools/go.mod and run
  via `go tool`, so local and CI invocations use the same versions.
- `make install/wat2wasm` provisions the wat2wasm CLI the test suite
  needs, dispatching to the host's package manager (Homebrew on
  macOS, apt/dnf/pacman/apk on Linux).
- Makefile targets for local development.

Test coverage is 85.2% of statements overall.

* README: document the WASI runtime, performance, and library entry points

- Add a "WASI support" subsection explaining the single-file,
  stdlib-only `wasi_snapshot_preview1` implementation and the
  resulting cross-platform reach.
- Add a "Performance" section with the wazero-vs-wasm2go corpus
  numbers (cold start 8.4×, short queries up to 81×, TPC-H scans
  within ±10%).

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

* ci: align release-test with release.yml — use stable Go

The release-test workflow exercises the same `make release/check`
dry-run that the publish job runs at tag time, so it should pull
the same toolchain. Switch it from `go-version-file: tools/go.mod`
to `go-version: stable` to match release.yml.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
2026-05-24 13:34:54 +09:00

41 lines
1.9 KiB
WebAssembly Text Format

(module
;; Mirrors C++ virtual method dispatch via call_indirect:
;; Each "object" has a vtable pointer at offset 0. The vtable is an
;; array of function indexes. Calling a virtual method:
;; vtable = *(obj + 0)
;; fn_idx = *(vtable + slot * 4)
;; call_indirect(fn_idx, obj, args...)
(memory (export "memory") 1)
(table 8 funcref)
(type $unop (func (param i32) (result i32)))
(type $binop (func (param i32 i32) (result i32)))
;; Two "classes": Cat returns 1 from area, Square returns side*side.
(func $cat_area (param $self i32) (result i32) (i32.const 1))
(func $cat_kind (param $self i32) (result i32) (i32.const 100))
(func $sq_area (param $self i32) (result i32)
(i32.mul (i32.load (i32.add (local.get $self) (i32.const 4)))
(i32.load (i32.add (local.get $self) (i32.const 4)))))
(func $sq_kind (param $self i32) (result i32) (i32.const 200))
(elem (i32.const 0) $cat_area $cat_kind $sq_area $sq_kind)
;; Object layout: { vtable_idx: i32 @0, side: i32 @4 }
;; cat at 32 { vtable=0 (cat_area, cat_kind), side=ignored }
;; sq at 48 { vtable=8 (sq_area, sq_kind), side=5 }
;; vtable_0 at 64: [0, 1] ;; index 0 → cat_area, 1 → cat_kind
;; vtable_1 at 72: [2, 3]
(data (i32.const 32) "\40\00\00\00\00\00\00\00") ;; vtable=64, side=0
(data (i32.const 48) "\48\00\00\00\05\00\00\00") ;; vtable=72, side=5
(data (i32.const 64) "\00\00\00\00\01\00\00\00") ;; [0, 1]
(data (i32.const 72) "\02\00\00\00\03\00\00\00") ;; [2, 3]
;; obj.method(slot) — vtable[slot] called as unop(obj).
(func (export "call_method") (param $obj i32) (param $slot i32) (result i32)
(local $vt i32)
(local $fn i32)
(local.set $vt (i32.load (local.get $obj)))
(local.set $fn (i32.load
(i32.add (local.get $vt) (i32.mul (local.get $slot) (i32.const 4)))))
(call_indirect (type $unop) (local.get $obj) (local.get $fn))))