punkshell

1498 Commits

1 Branch

1 Tag

228 MiB

Commit Graph

Author	SHA1	Message	Date
Julian Noble	8f446690c1	G-172 (active): record + surface + audit the distributed-binary CPU floor Approach 3 (record floor field): build905.zig declares cpu_floor="baseline" beside the default_target pin and writes cpu_floor + cpu_model into each family member's embedded record [provenance] (= target.result.cpu.model.name, so "x86_64" for the default build, "znver5" for -Dcpu=native - the floor is a default, not a restriction). family_artifacts.tcl derives both from the embedded record (G-117 single-source-of-truth) into the sidecar [provenance], failing if absent; family_check.tcl asserts them non-empty. Approach 4 (audit tool): scriptlib/developer/cpufloor_audit.tcl disassembles a binary's .text via a located objdump (llvm-objdump preferred, GNU fallback) or audits a pre-disassembled excerpt, classifies by AVX register width (zmm=v4, ymm=v3; baseline/v2 forbid both, v3 forbids zmm, v4 allows all), reports out-of-floor count + first RVA + sample mnemonics, exit 0 PASS / 1 FAIL. Bundled fixtures in cpufloor_fixtures/ are real disassembly excerpts (avx512, avx2, clean); selftest 12/12 cases pass. Verified on real binaries: rebuilt bin/punkzip.exe PASS (zmm=0); a -Dcpu=native probe FAILs at baseline (123 zmm) and PASSes at v4. Approach 5 (punk-runtime surfacing): both .ps1 and .bash twins updated and re-wrapped. Host CPU level detection (PS via IsProcessorFeaturePresent PF SSE2=10/SSE4.2=38/AVX2=40/AVX512F=41; bash via /proc/cpuinfo flags) feeds a meets/below/unknown/norecord verdict. fetch prints cpu floor (UNGATED - a cross-platform fetch for another machine stays free); list annotates rows the host cannot run (!CPU-FLOOR:v<req>, local rows only); use/run gate on below with a named diagnosis instead of a silent STATUS_ILLEGAL_INSTRUCTION (0xC000001D) - the 2026-08-06 AVX-512 regression failure mode; info adds the fields. bin/punk-runtime.cmd re-wrapped (deterministic; scriptwrap_runtime_cmd_roundtrip_no_drift test PASSES). Activation: overlap survey re-run at activation (goals_xref score G-172) - no goals drafted in the interval; existing Related: notes cover every pair. Project version 0.57.0 -> 0.57.1 (patch - user-visible punk-runtime behaviour shipped in kits). Remaining for acceptance: rebuild + republish in-situ (per Approach 6's alpha dispensation) and audit the republished artifacts to confirm zmm=0 - a publication-time, user-owned step. Assisted-by: harness=pi; primary-model=huggingface/zai-org/GLM-5.2; api-location=huggingface.co	5 days ago
Julian Noble	d949274f2b	G-172: correct the zig-gate rebuild-blocker claim; Approach 6 -> in-situ; r2 family + tools republished at baseline floor The drafting session recorded the recipes' required_zig gate as blocking any rebuild on this box (a prerelease sorts below 0.16.0; "newest zig otherwise present is 0.15.2"). Wrong: only the stray dev copy is rejected - the zigpin toolchain bin/tools/zig-x86_64-windows-0.16.0/zig.exe is a released 0.16.0, present and passing the gate (the zig-x86_64-windows-* naming family in bin/tools was missed and a removal back-inferred from the artifact records). Notes bullet and Progress corrected; nothing was removed and nothing blocks. Approach 6 rewritten per user decision: republication is in-situ replacement under existing artifact names/revisions - punkbin immutability deliberately violable during alpha (all consumers in-house, zero third-party users). Progress: Approach 6 executed for the r2 generation + tools (punkbin ab5611d pushed) - full bootstrap rebuild with the pinned zig, zmm=0 ymm=0 audits on all five binaries, family_check PASS, two consecutive core-gate PASS runs with identical totals (interp-36.7 bgerror-race jitter and a 4h httpProxy.test ThreadLevel-1 hang documented). Record-honesty residual noted: published tomls carry emission-time [tests] summaries - refresh folded into Approach 3. Remaining: floor field, audit tool, punk-runtime surfacing; r1 disposition + bin/punk9* kit rebake behind those. goals_lint: clean (81 active, 91 archived). Claude-Session: https://claude.ai/code/session_01WXribLxUjk3dZUsN3r6rKb Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com	5 days ago
Julian Noble	946a32da19	G-172 drafted (proposed) + the four recipe pins: distributed binaries get a baseline CPU floor The published tclsh9.0.5 runtime family is AVX-512-only. A flagless bin/punk-runtime.cmd fetch hands a fresh checkout the curated win32-x86_64 default (tclsh9.0.5-punk-r2.exe), which on a CPU without AVX-512 raises #UD and is killed with STATUS_ILLEGAL_INSTRUCTION (0xC000001D, errorlevel -1073741795) before writing a byte - no message, no prompt, no error. First reported as a Windows-version difference (25H2 works, 23H2 does not); it is not one. Cause: the recipes called b.standardTargetOptions(.{}) and no build path passed -Dtarget/-Dcpu, so zig resolved cpu_model .determined_by_arch_os by NATIVE detection and ReleaseFast auto-vectorised to the Zen 5 build host. Measured: all six published tclsh9.0.5-* artifacts (punk + plain, r1 + r2, both -bi- variants) carry 2756 zmm-operand instructions each - real EVEX encodings, first site at the front of .text, and Tcl has no runtime CPU dispatch - as do bin/punk905.exe, punk9-dev.exe, punk9_beta.exe, punk9bi_beta.exe, punkdeclare.exe and punkfiledemo.exe. bin/punkzip.exe carries 1724 and bin/punkres.exe 1423, so a bake on such a machine fails too. An older generation (punk901, punk9.exe, xcritcl.exe, tclsh90s) is AVX2-only from an earlier host: same defect, milder floor. Confirmed across three machines - Zen 2 dies, Zen 4 and Zen 5 run. Pins applied to all four in-repo recipes (suite_tcl90, suite_tcl86, punkzip, punkres): standardTargetOptions gains .default_target = .{ .cpu_model = .baseline }, so a flagless build is portable while -Dcpu=native remains the developer opt-in and -Dtarget=<triple> is unaffected. Floor chosen as baseline (x86-64 v1) - for a Tcl interpreter the codegen delta against v2/v3 is negligible set against the default runtime failing to start. This has to be a recipe DEFAULT rather than a build-command convention: "remember to pass -Dcpu= when publishing" is precisely what failed silently for six artifacts. Verified by zig ast-check on all four recipes, and by reproducing the mechanism with the same toolchain and optimize level on an equivalent recipe (flagless -> x86_64 baseline, zmm=0; -Dcpu=native -> znver5, zmm=805). No suite build was run: all four recipes gate on required_zig = "0.16.0" with a .lt SemVer compare, which rejects the bundled prerelease bin/tools/zig-0.16.0-dev.254 - a separate pre-existing defect, recorded in the goal's Notes and deliberately not fixed here. Nothing is rebuilt or republished, and no shipped surface changes, so no project version bump. Recording the floor in the artifact metadata record, an audit tool, punk-runtime surfacing it on use/run (fetch stays ungated - fetching for another platform is a normal workflow), and the rebuild/republish with the defaults.txt repoint all remain open as G-172. Assisted-by: harness=claude; primary-model=claude-opus-5[1m]; api-location=anthropic.com	5 days ago

Author

SHA1

Message

Date

Julian Noble

8f446690c1

G-172 (active): record + surface + audit the distributed-binary CPU floor

Approach 3 (record floor field): build905.zig declares cpu_floor="baseline"
beside the default_target pin and writes cpu_floor + cpu_model into each
family member's embedded record [provenance] (= target.result.cpu.model.name,
so "x86_64" for the default build, "znver5" for -Dcpu=native - the floor is a
default, not a restriction). family_artifacts.tcl derives both from the
embedded record (G-117 single-source-of-truth) into the sidecar [provenance],
failing if absent; family_check.tcl asserts them non-empty.

Approach 4 (audit tool): scriptlib/developer/cpufloor_audit.tcl disassembles a
binary's .text via a located objdump (llvm-objdump preferred, GNU fallback) or
audits a pre-disassembled excerpt, classifies by AVX register width (zmm=v4,
ymm=v3; baseline/v2 forbid both, v3 forbids zmm, v4 allows all), reports
out-of-floor count + first RVA + sample mnemonics, exit 0 PASS / 1 FAIL.
Bundled fixtures in cpufloor_fixtures/ are real disassembly excerpts (avx512,
avx2, clean); selftest 12/12 cases pass. Verified on real binaries: rebuilt
bin/punkzip.exe PASS (zmm=0); a -Dcpu=native probe FAILs at baseline (123 zmm)
and PASSes at v4.

Approach 5 (punk-runtime surfacing): both .ps1 and .bash twins updated and
re-wrapped. Host CPU level detection (PS via IsProcessorFeaturePresent PF
SSE2=10/SSE4.2=38/AVX2=40/AVX512F=41; bash via /proc/cpuinfo flags) feeds a
meets/below/unknown/norecord verdict. fetch prints cpu floor (UNGATED - a
cross-platform fetch for another machine stays free); list annotates rows the
host cannot run (!CPU-FLOOR:v<req>, local rows only); use/run gate on below
with a named diagnosis instead of a silent STATUS_ILLEGAL_INSTRUCTION
(0xC000001D) - the 2026-08-06 AVX-512 regression failure mode; info adds the
fields. bin/punk-runtime.cmd re-wrapped (deterministic;
scriptwrap_runtime_cmd_roundtrip_no_drift test PASSES).

Activation: overlap survey re-run at activation (goals_xref score G-172) - no
goals drafted in the interval; existing Related: notes cover every pair.

Project version 0.57.0 -> 0.57.1 (patch - user-visible punk-runtime behaviour
shipped in kits). Remaining for acceptance: rebuild + republish in-situ (per
Approach 6's alpha dispensation) and audit the republished artifacts to confirm
zmm=0 - a publication-time, user-owned step.

Assisted-by: harness=pi; primary-model=huggingface/zai-org/GLM-5.2; api-location=huggingface.co

5 days ago

Julian Noble

d949274f2b

G-172: correct the zig-gate rebuild-blocker claim; Approach 6 -> in-situ; r2 family + tools republished at baseline floor

The drafting session recorded the recipes' required_zig gate as blocking any
rebuild on this box (a prerelease sorts below 0.16.0; "newest zig otherwise
present is 0.15.2"). Wrong: only the stray dev copy is rejected - the zigpin
toolchain bin/tools/zig-x86_64-windows-0.16.0/zig.exe is a released 0.16.0,
present and passing the gate (the zig-x86_64-windows-* naming family in
bin/tools was missed and a removal back-inferred from the artifact records).
Notes bullet and Progress corrected; nothing was removed and nothing blocks.

Approach 6 rewritten per user decision: republication is in-situ replacement
under existing artifact names/revisions - punkbin immutability deliberately
violable during alpha (all consumers in-house, zero third-party users).

Progress: Approach 6 executed for the r2 generation + tools (punkbin ab5611d
pushed) - full bootstrap rebuild with the pinned zig, zmm=0 ymm=0 audits on
all five binaries, family_check PASS, two consecutive core-gate PASS runs
with identical totals (interp-36.7 bgerror-race jitter and a 4h
httpProxy.test ThreadLevel-1 hang documented). Record-honesty residual noted:
published tomls carry emission-time [tests] summaries - refresh folded into
Approach 3. Remaining: floor field, audit tool, punk-runtime surfacing; r1
disposition + bin/punk9* kit rebake behind those.

goals_lint: clean (81 active, 91 archived).

Claude-Session: https://claude.ai/code/session_01WXribLxUjk3dZUsN3r6rKb
Assisted-by: harness=claude; primary-model=claude-fable-5; api-location=anthropic.com

5 days ago

Julian Noble

946a32da19

G-172 drafted (proposed) + the four recipe pins: distributed binaries get a baseline CPU floor

The published tclsh9.0.5 runtime family is AVX-512-only. A flagless
bin/punk-runtime.cmd fetch hands a fresh checkout the curated win32-x86_64
default (tclsh9.0.5-punk-r2.exe), which on a CPU without AVX-512 raises #UD and
is killed with STATUS_ILLEGAL_INSTRUCTION (0xC000001D, errorlevel -1073741795)
before writing a byte - no message, no prompt, no error. First reported as a
Windows-version difference (25H2 works, 23H2 does not); it is not one.

Cause: the recipes called b.standardTargetOptions(.{}) and no build path passed
-Dtarget/-Dcpu, so zig resolved cpu_model .determined_by_arch_os by NATIVE
detection and ReleaseFast auto-vectorised to the Zen 5 build host. Measured: all
six published tclsh9.0.5-* artifacts (punk + plain, r1 + r2, both -bi- variants)
carry 2756 zmm-operand instructions each - real EVEX encodings, first site at the
front of .text, and Tcl has no runtime CPU dispatch - as do bin/punk905.exe,
punk9-dev.exe, punk9_beta.exe, punk9bi_beta.exe, punkdeclare.exe and
punkfiledemo.exe. bin/punkzip.exe carries 1724 and bin/punkres.exe 1423, so a
bake on such a machine fails too. An older generation (punk901*, punk9.exe,
xcritcl.exe, tclsh90s*) is AVX2-only from an earlier host: same defect, milder
floor. Confirmed across three machines - Zen 2 dies, Zen 4 and Zen 5 run.

Pins applied to all four in-repo recipes (suite_tcl90, suite_tcl86, punkzip,
punkres): standardTargetOptions gains .default_target = .{ .cpu_model =
.baseline }, so a flagless build is portable while -Dcpu=native remains the
developer opt-in and -Dtarget=<triple> is unaffected. Floor chosen as baseline
(x86-64 v1) - for a Tcl interpreter the codegen delta against v2/v3 is
negligible set against the default runtime failing to start. This has to be a
recipe DEFAULT rather than a build-command convention: "remember to pass -Dcpu=
when publishing" is precisely what failed silently for six artifacts.

Verified by zig ast-check on all four recipes, and by reproducing the mechanism
with the same toolchain and optimize level on an equivalent recipe (flagless ->
x86_64 baseline, zmm=0; -Dcpu=native -> znver5, zmm=805). No suite build was
run: all four recipes gate on required_zig = "0.16.0" with a .lt SemVer compare,
which rejects the bundled prerelease bin/tools/zig-0.16.0-dev.254 - a separate
pre-existing defect, recorded in the goal's Notes and deliberately not fixed
here.

Nothing is rebuilt or republished, and no shipped surface changes, so no project
version bump. Recording the floor in the artifact metadata record, an audit tool,
punk-runtime surfacing it on use/run (fetch stays ungated - fetching for another
platform is a normal workflow), and the rebuild/republish with the defaults.txt
repoint all remain open as G-172.

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

5 days ago

3 Commits (8f446690c1a9e671fda9710116232c3000c876ab)