mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-09-29 07:10:32 -04:00
33c292dea5
BYTE-IDENTICAL on all four, with NOTHING banked (clean rm -rf asm/<bin> + extract + build -j + check), which is the whole point: the structure lands first and proves neutral, then drafts bank against it. split_indicator: 213 OK, 0 needing attention, of 213 — the CARVE-BLOCKED class is now EMPTY fleet-wide. One code object contributes exactly ONE contiguous .rodata run, so a subseg owning raw jump tables in two non-adjacent spans could carve only one of them and every switch function in the other span was unbankable at any effort (cookbook §426/§431). ov_SC01_084 2 pieces cut 0x80182A00 (0x5A8A8) ov_SC02_005 3 PIECES cuts 0x80185060 (0x5CF08) + 0x80185E80 (0x5DD28) ov_SC02_011 3 PIECES cuts 0x80183178 (0x5B020) + 0x80188E3C (0x60CE4) ov_SC03_105 2 pieces cut 0x8018624C (0x5E0F4) TWO OF THE FOUR NEEDED A CUT THE BRIEF DID NOT NAME, and the address evidence found it: each already had a carve run that could not merge with span 1, separated by rodata that is not padding — ov_SC02_005 by `0000F040 00000000` (8 bytes, twice the widest .align 3 pad the JTBL_PADS spec can emit), ov_SC02_011 by `FEBEF6AE 000002DC 0 0` (a TU's trailing const data). A gap detector keyed on zero words would have merged them and produced an unbuildable carve: the load-bearing test is "is this word a valid code address in this overlay's text range", not "is it zero". ov_SC01_084's divider is real data too (`0 FFFF0000 00080000 0 0`), while ITS span-1 gap word IS a zero .align 3 pad and merges. OVERLAY SPLITS ARE NEAR-FREE, AND THE REASON IS STRUCTURAL — the opposite of main. The Phase-26 §8b carried decl layer re-emits each region's externs locally, so only typedefs cross a cut: 1 name of 2,679 (ov_SC01_084, 0 typedefs) · 5 typedefs of 44 (ov_SC02_005) · 2 names of 3,254, 0 typedefs (ov_SC02_011) · 0 of 3,074 with zero compiler errors (ov_SC03_105). main's split moved 57 of 1,247. Every crossing typedef was MOVED to a <bin>_shared.h, never copied, and every list came from the compiler (R33). Carve probes (jtbl_carve --func, then reverted — carve state is added when a function banks, never speculatively): all four subsegs now accept a carve with no fail-loud, and jtbl_carve derived the §8e per-table pad specs the zero-word rule predicts. Unlocks 17 open switch functions: ov_SC01_084 func_80182A00 · ov_SC02_005 func_80185060, func_80185E80 · ov_SC02_011 func_80183178, func_80183630, func_8018418C, func_80188E3C · ov_SC03_105 func_801806F8, func_80180ABC, func_80180EC0, func_801813BC, func_801818E8, func_80181C84, func_8018624C, func_801867D0 (+2 more span-1 owners). CORRECTION, measured not assumed: config/wave_exclude.txt listed ov_SC01_084:func_80182328 as CARVE-BLOCKED and it never was — its table ABUTS the existing carve, so it always merged into one run. Proven by control on the PRISTINE unsplit config: --func func_80182A00 exits 1 "would host NON-CONTIGUOUS .rodata carves", --func func_80182328 succeeds.