From 9b9ba0c2ea68a2d68660f84c804e9195fa869b70 Mon Sep 17 00:00:00 2001 From: Christopher Williams Date: Thu, 24 Sep 2026 19:12:18 -0400 Subject: [PATCH] phase12: correct the body count in 354e90d's message (672/681, not 670/680) --- phase-ends/logs/Phase12.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/phase-ends/logs/Phase12.md b/phase-ends/logs/Phase12.md index 8212554..8733cea 100644 --- a/phase-ends/logs/Phase12.md +++ b/phase-ends/logs/Phase12.md @@ -1287,3 +1287,15 @@ infer it from an adjacent symbol's name.** **`--cc1-flag=X` REPLACES the default `-quiet -O2 -G0` set.** A's first `-fthread-jumps` probe came back 200 bytes purely because `-O2` had been dropped, which reads like a codegen disaster and is only a flag-set replacement. Any diagnosis run must pass all four flags explicitly. + +### A wrong count in my own commit message, corrected here + +Commit `354e90d`'s message says "670 bodies / 680 regions". **The true figures after that merge are +672 bodies / 681 regions.** I wrote the message's headline from the pre-merge number in my head instead +of from the command output in front of me, and the merge then added three more rows +(`0x80107CCC`, `0x8002D060`, `0x8006FAEC`). + +Not rewriting history for a number, but recording it, because **a wrong body count in the commit log is +exactly the kind of figure a later session trusts without re-deriving**, and the phase's whole +projection rests on this number being the one the gate produced. The authority is +`config/regions.tsv` counted at the merge, and that said 681 regions / 672 bodies.