punkshell

1291 Commits

1 Branch

1 Tag

220 MiB

Commit Graph

Author	SHA1	Message	Date
Julian Noble	f89bd58c31	G-100 achieved: suite_tcl86 dependency set (Tk 8.6, tklib, tcllib + tcllibc) and an 8.6 runtests census Extends the 8.6 buildsuite with the remaining pieces punkshell's Tcl 8 testing depends on, all built from source with the pinned zig 0.16.0 toolchain only. Tk 8.6.17 (build_tk86/build_tk86.zig) is a RE-DERIVATION from the staged 8.6 win/makefile.vc + rules.vc, not a port of suite_tcl90's build_tk.zig: - no generic/tkPkgConfig.c in 8.6 -> no CFG_* defines at all - rules.vc TCL_MAJOR_VERSION==8 arm -> tk86t.dll + lib/tk8.6 (vs tcl9tk90.dll) - @TK_WIN_VERSION@ substitutes $(DOTVERSION).0.0, not the tcl-style <dotversion>.<releaselevel>.<patchlevel> formula - 8.6 TKOBJS carries no tkIcu/tkImgListFormat/tkImgSVGnano/tkWinGDI/tkWinIco/ tkWinSysTray; XLIBOBJS is a first-class makefile macro here (the 9.0 derivation had to recover those files by hand) USE_TCL_STUBS + USE_TCLOO_STUBS against libtclstub86.a is the stock rules.vc arrangement and keeps the dll loadable by both suite shells. tkMain.c is compiled twice per makefile.vc, the ansi copy forced with -UUNICODE/-U_UNICODE (verified the pinned zig cc defines neither for x86_64-windows-gnu, so the 8.6 core's ANSI/TCHAR arrangement is matched exactly). tklib 0.9 and tcllib 2.0 install via their own installer.tcl (batch, packages only, explicit -pkg-path so the installer's tcl_pkgPath-derived default can never write off-tree); tcllibc is built by critcl 3.3.1 driving zig cc (tracked critcl_zig.config, target pinned win32-x86_64-zig - critcl otherwise probes PATH and falls back to its builtin msvc target). critcl compiles against its own bundled headers chosen by the driving shell's version, which is why one config serves both generations. New evidence tools, run on every build: tools/tk_smoke.tcl maps a real toplevel with classic + themed widgets, updates, then destroys it - a load-only check passes even with no usable display tools/accel_bench.tcl same payload through sha1's critcl and pure-Tcl implementations with the digests compared: 4MB -> critcl 5.7ms vs pure-tcl 2736ms = 477x Test tiers (G-107 policy pattern): test-tcllib/test-tklib on the record tier inside test-libraries, plus an opt-in test-tk (winDialog/winMsgbox excluded by default - their message-injection automation blocks on a human under a batch shell). First censuses on tclsh86ts.exe 8.6.18: thread 142 run / 0 failed GATE PASS tklib 796 run / 0 failed record tcllib 64259 run / 41 failed record (names in the summary artifact) tclvfs 51 run / 4 failed GATE PASS after baseline extension The tclvfs baseline grew vfsFtp-1.1..1.3: they sit behind an 'ftp' constraint needing tcllib's ftp package - absent at the G-099 capture, satisfied now that the suite installs tcllib - so they run and reach the retired ftp.tcl.tk, the same external-service class already baselined for vfsUrl-1.2/2.1. punkshell runtests census (both runs 2026-07-26, identical flags, default single-process sequential - 8.6 has no tcl::process so -jobs re-convoys): native Tcl 8.6.17 1003 total / 986 passed / 10 skipped / 7 failed suite tclsh86ts 1003 total / 987 passed / 10 skipped / 6 failed runtests_parity.tcl finds exactly ONE difference: punkcheck concurrency_two_writers_no_corruption failed in the BASELINE run and passed on the suite runtime - a full-suite-load flake (6/6 twice in isolation on both runtimes). Zero suite-runtime-only failures. Tk-dependent suites ran unskipped (repl consolebackends 3/3, including the tkconsole backend on the suite Tk). Two defects fixed in passing: - scrubTclEnv never cleared TCL<major>_<minor>_TM_PATH, so suite shells silently preferred machine/repo tm modules over what the suite had just installed (a repo-built sha1-2.0.4.tm shadowed tcllib's 2.0.5, md5 2.0.8 shadowed 2.0.9) - any census through such a shell measures the machine. The scrub list now covers TCL8_0..8_7 + TCL9_0/9_1 in all three sites (per-step, suite.tcl process-level, bootstrap nested build). suite_tcl90 has the same exposure via TCL9_0_TM_PATH and is deliberately untouched here (out of this goal's scope) - pointers recorded in G-108 and G-116. - build.zig.zon's .fingerprint was hand-authored, so 'zig build' from the tracked suite dir died with 'invalid fingerprint' - the no-tclsh bootstrap flow could never have run. Corrected to zig's computed value (its low half is a checksum of the package name); 'zig build stage' now verified. Goal flipped to achieved 2026-07-26 and archived; reference sweep updated G-005, G-101, G-105 and ARCHITECTURE.md, and the archive-time xref pair G-101 <-> G-116 (whose only bridges were the archived G-100/G-103) gained a direct Related pointer. No project-version bump - arm's-length build tooling, not shipped shell behaviour. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	2 weeks ago

Author

SHA1

Message

Date

Julian Noble

f89bd58c31

G-100 achieved: suite_tcl86 dependency set (Tk 8.6, tklib, tcllib + tcllibc) and an 8.6 runtests census

Extends the 8.6 buildsuite with the remaining pieces punkshell's Tcl 8 testing
depends on, all built from source with the pinned zig 0.16.0 toolchain only.

Tk 8.6.17 (build_tk86/build_tk86.zig) is a RE-DERIVATION from the staged 8.6
win/makefile.vc + rules.vc, not a port of suite_tcl90's build_tk.zig:

  - no generic/tkPkgConfig.c in 8.6 -> no CFG_* defines at all
  - rules.vc TCL_MAJOR_VERSION==8 arm -> tk86t.dll + lib/tk8.6 (vs tcl9tk90.dll)
  - @TK_WIN_VERSION@ substitutes $(DOTVERSION).0.0, not the tcl-style
    <dotversion>.<releaselevel>.<patchlevel> formula
  - 8.6 TKOBJS carries no tkIcu/tkImgListFormat/tkImgSVGnano/tkWinGDI/tkWinIco/
    tkWinSysTray; XLIBOBJS is a first-class makefile macro here (the 9.0
    derivation had to recover those files by hand)

USE_TCL_STUBS + USE_TCLOO_STUBS against libtclstub86.a is the stock rules.vc
arrangement and keeps the dll loadable by both suite shells. tkMain.c is
compiled twice per makefile.vc, the ansi copy forced with -UUNICODE/-U_UNICODE
(verified the pinned zig cc defines neither for x86_64-windows-gnu, so the 8.6
core's ANSI/TCHAR arrangement is matched exactly).

tklib 0.9 and tcllib 2.0 install via their own installer.tcl (batch, packages
only, explicit -pkg-path so the installer's tcl_pkgPath-derived default can
never write off-tree); tcllibc is built by critcl 3.3.1 driving zig cc (tracked
critcl_zig.config, target pinned win32-x86_64-zig - critcl otherwise probes PATH
and falls back to its builtin msvc target). critcl compiles against its own
bundled headers chosen by the driving shell's version, which is why one config
serves both generations.

New evidence tools, run on every build:

  tools/tk_smoke.tcl     maps a real toplevel with classic + themed widgets,
                         updates, then destroys it - a load-only check passes
                         even with no usable display
  tools/accel_bench.tcl  same payload through sha1's critcl and pure-Tcl
                         implementations with the digests compared:
                         4MB -> critcl 5.7ms vs pure-tcl 2736ms = 477x

Test tiers (G-107 policy pattern): test-tcllib/test-tklib on the record tier
inside test-libraries, plus an opt-in test-tk (winDialog/winMsgbox excluded by
default - their message-injection automation blocks on a human under a batch
shell). First censuses on tclsh86ts.exe 8.6.18:

  thread     142 run /  0 failed   GATE PASS
  tklib      796 run /  0 failed   record
  tcllib   64259 run / 41 failed   record (names in the summary artifact)
  tclvfs      51 run /  4 failed   GATE PASS after baseline extension

The tclvfs baseline grew vfsFtp-1.1..1.3: they sit behind an 'ftp' constraint
needing tcllib's ftp package - absent at the G-099 capture, satisfied now that
the suite installs tcllib - so they run and reach the retired ftp.tcl.tk, the
same external-service class already baselined for vfsUrl-1.2/2.1.

punkshell runtests census (both runs 2026-07-26, identical flags, default
single-process sequential - 8.6 has no tcl::process so -jobs re-convoys):

  native Tcl 8.6.17   1003 total / 986 passed / 10 skipped / 7 failed
  suite tclsh86ts     1003 total / 987 passed / 10 skipped / 6 failed

runtests_parity.tcl finds exactly ONE difference: punkcheck
concurrency_two_writers_no_corruption failed in the BASELINE run and passed on
the suite runtime - a full-suite-load flake (6/6 twice in isolation on both
runtimes). Zero suite-runtime-only failures. Tk-dependent suites ran unskipped
(repl consolebackends 3/3, including the tkconsole backend on the suite Tk).

Two defects fixed in passing:

  - scrubTclEnv never cleared TCL<major>_<minor>_TM_PATH, so suite shells
    silently preferred machine/repo tm modules over what the suite had just
    installed (a repo-built sha1-2.0.4.tm shadowed tcllib's 2.0.5, md5 2.0.8
    shadowed 2.0.9) - any census through such a shell measures the machine. The
    scrub list now covers TCL8_0..8_7 + TCL9_0/9_1 in all three sites (per-step,
    suite.tcl process-level, bootstrap nested build). suite_tcl90 has the same
    exposure via TCL9_0_TM_PATH and is deliberately untouched here (out of this
    goal's scope) - pointers recorded in G-108 and G-116.
  - build.zig.zon's .fingerprint was hand-authored, so 'zig build' from the
    tracked suite dir died with 'invalid fingerprint' - the no-tclsh bootstrap
    flow could never have run. Corrected to zig's computed value (its low half
    is a checksum of the package name); 'zig build stage' now verified.

Goal flipped to achieved 2026-07-26 and archived; reference sweep updated G-005,
G-101, G-105 and ARCHITECTURE.md, and the archive-time xref pair G-101 <-> G-116
(whose only bridges were the archived G-100/G-103) gained a direct Related
pointer. No project-version bump - arm's-length build tooling, not shipped shell
behaviour.

Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com

2 weeks ago

1 Commits (f07768786a4fd8ab70d123b964609064c6dbc059)