mirror of
https://github.com/hanzoai/wasm2go.git
synced 2026-10-30 15:06:48 +00:00
* 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]>
35 lines
1.3 KiB
WebAssembly Text Format
35 lines
1.3 KiB
WebAssembly Text Format
;; cg_frame.wat — the Emscripten C++ stack-frame allocation idiom:
|
|
;; global.set $sp (local.tee $fp (i32.sub (global.get $sp) (i32.const N)))
|
|
;; wasm2go recognizes this and emits the compact `lL = subg(&m.gK, N)`
|
|
;; rewrite (tryEmitFrameAlloc). Both an i32 stack pointer and the
|
|
;; add-of-negative-constant variant are exercised.
|
|
(module
|
|
(global $sp (mut i32) (i32.const 65536))
|
|
(global $sp64 (mut i64) (i64.const 1048576))
|
|
(memory 1)
|
|
|
|
;; Classic frame alloc: reserve 32 bytes, return the new frame pointer.
|
|
(func (export "alloc_frame") (result i32)
|
|
(local $fp i32)
|
|
(global.set $sp (local.tee $fp (i32.sub (global.get $sp) (i32.const 32))))
|
|
(local.get $fp))
|
|
|
|
;; Frame alloc via add-of-negative-constant (the i32.add form).
|
|
(func (export "alloc_frame_add") (result i32)
|
|
(local $fp i32)
|
|
(global.set $sp (local.tee $fp (i32.add (global.get $sp) (i32.const -48))))
|
|
(local.get $fp))
|
|
|
|
;; Release the frame back.
|
|
(func (export "free_frame") (param $n i32)
|
|
(global.set $sp (i32.add (global.get $sp) (local.get $n))))
|
|
|
|
(func (export "sp_now") (result i32) (global.get $sp))
|
|
|
|
;; i64-global frame alloc (subg64 path).
|
|
(func (export "alloc64") (result i64)
|
|
(local $fp i64)
|
|
(global.set $sp64 (local.tee $fp (i64.sub (global.get $sp64) (i64.const 64))))
|
|
(local.get $fp))
|
|
)
|