Hojun-Cho/ww
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: fold driver-parity byteid into 989_lib_byteid, retire 815/940/951

Browse Source 
Wwstage-driver-leg byte identity gets one owner. The three carriers'
content identity is already blanket-owned by their r815_/r940_/r951_
corpus twins via test-data-byteid; their only non-redundant assertion
was the ww_ww driver leg, which 989_lib_byteid's 43-unit sweep covers
apart from the zero-dep root-only edge — folded in as a new probe row
(44 units). r940 fixture comments re-cited off the retired carrier.
This commit is contained in:
Hojun-Cho
2026-08-08 00:36:11 +09:00
parent 66251cc52b
commit 0b23f9fb31
11 changed files with 26 additions and 699 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/test-system-v2.md
View File

@@ -36,17 +36,21 @@ The live declarative compiler corpus has 1,229 fixtures and 2,458 C/WW cells:
314 expected rejections (290 shared and 24 stage-specific), 12 compile-only
successes, 137 exit-zero programs, and 766 explicit-exit programs.
174 native C carriers remain. They are partitioned exactly once as five
in-process units, 27 byte/artifact gates, six bootstrap gates, one platform
171 native C carriers remain. They are partitioned exactly once as five
in-process units, 24 byte/artifact gates, six bootstrap gates, one platform
gate, and 135 residual compiler, package-layout, ABI, diagnostic-observer,
driver, linker, or FFI gates. Rows migrated to fixtures or native `@test`
owners were removed from those carriers; there is no compatibility execution
path for retired rows. 61 former byte/artifact carriers whose only assertion
was a cstage-vs-wwstage `.s` byte-compare of corpus fixtures were retired
into the blanket `test-data-byteid` comparator; the 27 survivors observe
into the blanket `test-data-byteid` comparator; the survivors observe
something the blanket cannot: assembly patterns, symbol tables, frame
layouts, `.wwi` round-trips, inline sources with no corpus twin, or the
wwstage-driver leg.
wwstage-driver leg. Wwstage-driver-leg byte identity (`ww_ww` versus `ww`
over the emitted `.s` set) has one owner, `989_lib_byteid`, whose unit
sweep spans lib test fixtures, import probes, and a zero-dep root-only
build; the former 815/940/951 driver-parity carriers were folded into it,
their content identity already owned by their corpus twins.
## Public targets