Hojun-Cho
2c33228b7e
Plan 9-style w-prefix on the per-arch tools, disambiguating from the
real Plan 9 6c/6a/6l in ref/plan9front/:
cmd/wwc/ → cmd/wcc/ libwwc.a → libwcc.a
cmd/6{c,a,l} → cmd/w6{c,a,l} binary names too
test/wwc/ → test/wcc/ 6 test files w/ w6 prefix
selfhost/cmd mirror in lockstep
bootstrap/amd64/{w6c,w6a,w6l} snapshot binaries (gitignored)
WW_6{C,A,L} → WW_W6{C,A,L} env-var overrides
Plan 9 source-tree refs ("Plan 9 6c shape", ref/plan9front/, etc.)
preserved. Hare-style driver, both C and ww sides:
ww test [path] discover *_test.ww in a directory module, run
each; single-file mode for `ww test foo.ww`
Module-by-name `ww build foo` resolves to foo.ww or foo/foo.ww
via search path (cwd : -I dirs : $WW_LIB)
Default-to-cwd `ww build` / `ww test` build the cwd module
Run pass-through `ww run path arg1 arg2` reaches the program
lib/os: getcwd (79) and getdents64 (217) syscalls power `.` resolution
and directory enumeration on the ww side.
Makefile: wwstage tool deps now include lib/os/os.ww (+ lib/strconv
for wwdump_ww) so lib/* edits force their rebuild instead of leaving
stale binaries — surfaced when test 995 first failed against a stale
w6c_ww built before the lib/os additions.
Test 993 byte-identical parity gate (C-side ww vs ww-side ww_ww on a
build corpus) stays green; all 19 tests pass.
1.4 KiB
bootstrap/
Stage-0 binaries for cold-start builds without cc. One subdirectory
per supported architecture; each holds four statically-linked ELF
executables that match the wwstage layout:
bootstrap/amd64/
ww driver, equivalent to out/bin/ww_ww
w6c compiler, out/bin/w6c_ww
w6a assembler, out/bin/w6a_ww
w6l linker, out/bin/w6l_ww
The binaries are intentionally gitignored until the compiler stops
churning enough to make the trust surface stable — see PLAN.md and
the v1.0 plan in BOOTSTRAP.md. To put them under your local working
copy, run make bootstrap-snapshot after a green make wwstage; to
ship them, git add -f bootstrap/amd64/{ww,w6c,w6a,w6l} explicitly.
Workflow
A fresh-checkout flow that never invokes cc:
make nocc # uses bootstrap/<arch>/* as the stage-0 entry
# and proves it reproduces itself byte-for-byte
The non-nocc default (make) still drives cc → cstage → wwstage.
Both paths coexist — make nocc lands in out/nocc/ so the cstage
build under out/ is undisturbed.
When to refresh the snapshot
The stage-0 binaries are frozen at the cgen state they were built
with. A make nocc failure usually means the live selfhost/cmd/wcc
cgen has drifted from the snapshot — regenerate with
make bootstrap-snapshot and re-verify.