Files
wasm2go/testdata/cg_nestedloop.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

68 lines
2.7 KiB
WebAssembly Text Format

;; cg_nestedloop.wat — control-flow shapes that the structured SSA emitter
;; cannot cleanly reconstruct (nested loops, sequential loops), forcing the
;; goto-based emitMultiBlock fallback path. Uses only opcodes inside the
;; narrow SSA-lowering set (i32 add/sub/mul/lt, local get/set, block/loop/
;; br/br_if) so the function actually reaches SSA codegen.
(module
;; Two nested loops: outer counts i in [0,n), inner counts j in [0,i),
;; accumulating i*j-ish work. Nested loops are explicitly out of scope
;; for the structured emitter.
(func (export "nested") (param $n i32) (result i32)
(local $i i32)
(local $j i32)
(local $acc i32)
(block $outer_done
(loop $outer
(br_if $outer_done (i32.ge_s (local.get $i) (local.get $n)))
(local.set $j (i32.const 0))
(block $inner_done
(loop $inner
(br_if $inner_done (i32.ge_s (local.get $j) (local.get $i)))
(local.set $acc
(i32.add (local.get $acc)
(i32.add (local.get $i) (local.get $j))))
(local.set $j (i32.add (local.get $j) (i32.const 1)))
(br $inner)))
(local.set $i (i32.add (local.get $i) (i32.const 1)))
(br $outer)))
(local.get $acc))
;; Two sequential (non-nested) loops in one function: first sums 0..n,
;; then doubles the running total m times.
(func (export "seq2") (param $n i32) (param $m i32) (result i32)
(local $i i32)
(local $acc i32)
(block $d1
(loop $l1
(br_if $d1 (i32.ge_s (local.get $i) (local.get $n)))
(local.set $acc (i32.add (local.get $acc) (local.get $i)))
(local.set $i (i32.add (local.get $i) (i32.const 1)))
(br $l1)))
(local.set $i (i32.const 0))
(block $d2
(loop $l2
(br_if $d2 (i32.ge_s (local.get $i) (local.get $m)))
(local.set $acc (i32.add (local.get $acc) (local.get $acc)))
(local.set $i (i32.add (local.get $i) (i32.const 1)))
(br $l2)))
(local.get $acc))
;; Multi-exit loop: the loop can leave to two distinct follow blocks
;; ($hit and $miss) depending on which condition fires. The structured
;; emitter rejects multi-exit loops, so this routes through the
;; goto-based emitMultiBlock.
(func (export "multiexit") (param $n i32) (param $target i32) (result i32)
(local $i i32)
(block $miss
(block $hit
(loop $l
(br_if $hit (i32.eq (local.get $i) (local.get $target)))
(br_if $miss (i32.ge_s (local.get $i) (local.get $n)))
(local.set $i (i32.add (local.get $i) (i32.const 1)))
(br $l)))
;; reached via $hit
(return (i32.mul (local.get $i) (i32.const 10))))
;; reached via $miss
(i32.const -1))
)