Files
BFM-decomp/config
Drew T a931423c7a feat(jtbl): the 154-A island split WORKS — byte-proven on md_SC03_076/func_801F218C
The whole split is ONE inserted config line plus jr_isolate_all --only, exactly as
the adversarial review concluded (no _pre piece, no ld_interleave change, the
- [0x0, .rodata, md_SC03_076] island piece untouched):

  - [0x268, .rodata, md_SC03_076_jr_801F218C]
  - [0x2d24, c, md_SC03_076_jr_801F218C]

FRESH negative control, measured now rather than inherited (the study's +8/0x144
baseline was measured on func_801F0F28 and misattributed):

  baseline  whole-binary sha1 9a165e368009a79bcc2ebb06bcb13e6da20d460e (green)
            md_SC03_076.o .rodata sh_size 0x27c  (the whole island)
  after     whole-binary sha1 9a165e368009a79bcc2ebb06bcb13e6da20d460e (green)
            md_SC03_076.o .rodata sh_size 0x268
            md_SC03_076_jr_801F218C.o .rodata sh_size 0x14  (the 5-entry table)

So the SHA is unchanged AND the object-level discriminator proves the split really
happened — the pair rules out the no-op reading of a green build.

Island census for the record (file offsets): D_801EF468 0x000-0x0D8, D_801EF540
0x0D8-0x144, then the migrated tables of func_801EFBB4 0x144, func_801F0210 0x1B4,
func_801F0734 0x1EC, func_801F0A9C 0x214, func_801F0F28 0x23C, func_801F218C 0x268
-> 0x27C = the island end. The island is a STACK: only the end-adjacent table carves
cheaply, and each isolation exposes the next one, so the module peels from the end.
2026-08-24 10:58:29 -06:00
..