☀️ 74% – adopt seventy-four exact owners on 7d8a72083: eight main-image functions and sixty-six scene sequences

[wowwheaties]

Summary

One commit on main (7d8a720): 74 owners adopted at differing_halfwords=0 that main does not have — 66 overlay scene sequences and 8 main-image functions. README 73.07% → 73.76%.

This is PR #6 reduced to what main still lacks after your own harvest (the claude/75-percent-coverage-m7axsj line, now merged, plus the 05 Sep adoptions on main): every owner main reached itself is dropped (your versions stay), leaving the 74 this branch carries that on 9eca142 are still retained assembly or name-only registrations.

Every overlay owner was re-adopted on this tip through this branch's own thumb2c adopt <owner> --span <registered span> --source <file> --name <name>; the 7 main-image functions are spelled Func_<address> in source with no alias line and register under semantic names (Graphics_CopyRectKeepLow, SaveState_LoadSelectedSlot, Menu_RunResourceModePrompt, Map_GetFocusedObjectTile, Map_FindMatchingTrigger, BattleEffect_Dispatch, PsynergyMenu_DrawVisibleActionPage, InventoryMenu_ShowModalMessage, Shop_SelectPartyMemberItem, BattlePresentation_BuildOpponentEntries, MusicPlayer_SetPitchAndUpdateFrequency), their games/gs1/asm/<addr>.s and recon drafts retired.

Registry notes:

• Retained overlay-assembly regions around adopted owners were shortened, cloned, or retired (45 region edits, evidence line appended on each), the same edit as before.
• Owners whose registered sequence letter main already uses for a different owner took the next free letter; each region edit carries an evidence line.
• Name-only RunEventScript registrations wholly inside adopted owners were absorbed by thumb2c adopt as before.
• main:080b8db8 (BattlePresentation_ApplyUnitDamage, 268 B) was recorded in games/gs1/asm/classification.json as a proven-retained compiler_entry_scheduling_module ("approved compiler cannot express the reference entry schedule without forbidden register constraints"). An ordinary C89 spelling links byte-exact: taking the context as a u8 * parameter and reassigning it from the local context block keeps GCC 2.96 from folding the known zero into the compared pointer, so the entry emits the reference's fresh movs r3, #0. The record retires with its assembly (group files 2 → 1, expected_bytes 976 → 708); the other member of that group, 080ba2c0, is untouched.
• resource_3ba:02002aec is adopted at its 190-byte extent inside its 192-byte registered region (the halfword after bx is alignment), the same shape as resource_378:0200290c earlier in this PR.

Gates (on 7d8a720)

• make overlay-check: audited rows with findings: 0
• make full-rom-check: byte_identical=yes, unowned_bytes=0
• make build-claimed, make build-asm, make coverage, make verify: green

Compiler note (early literal pools)

Several large scene functions match instruction-for-instruction but the ROM dumps a literal pool much earlier than the SImode range requires (b.n over a mid-function pool). Reading gcc/config/arm/arm.c (push_minipool_fix, create_fix_barrier) and arm.md: the pool head is the tightest fix, and *thumb_movhi_insn alt 1 / *thumb_zero_extendhisi2 carry pool ranges of 64 / 60 bytes. A plain u16 local is promoted to SImode, so the ordinary-C spellings that reproduce the ROM are a one-element array for a constant used as a value — u16 p[1]; p[0] = (u16)(s32)Data_00000000; — and the bare 16-bit constant for a u16 store (*shown = 0xe00; rather than (u16)(s32)Data_00000e00). This made resource_3c9:0200423c and resource_3c9:020008b4 exact here and moved four others to within a handful of halfwords; the converter could emit it for HImode pool fixes.

Near-exact drafts (not adopted; residue is allocation or scheduling only)

Available on request as seeds for your queue, each scored at its registered span: resource_373:020015dc 5240 B dh 10, resource_380:020027f8 5932 B dh 28, resource_3a4:02001838 1236 B dh 20, resource_371:020039fc 1296 B dh 66, resource_371:020028e8 972 B dh 19, resource_3af:020022c0 856 B dh 26, resource_3b1:02004254 892 B dh 2, resource_383:02001348 1608 B dh 2, resource_380:02001d04 1400 B dh 6, resource_377:02000a0c 1064 B dh 16, resource_3b9:02000dcc 992 B dh 6, resource_39f:02002500 dh 4 at 1700 B (its registered span of 1640 stops 60 bytes before the pool).

Review notes

• Compiler here is an Ubuntu 24.04 host rebuild of the pinned alchemy-gcc (dist hash f9086851…, distinct from the a3c3cfd9… rebuild this branch admits); the full ROM is byte-identical locally. Please re-verify with your bundle.
• Built on 7d8a720; a rebase onto a newer tip is mechanical — say the word.
• ☀️ 73% – adopt seventy-eight exact owners on 2338f8f0a: ten main-image functions and sixty-eight scene sequences #10 (the same owners on claude/75-percent-coverage-m7axsj) closed with that branch; this PR is the single remaining line.

🤖 Generated with Claude Code

[wowwheaties]

Independent re-check of every overlay owner this branch adopts (152, listed from source-paths.json vs 9dbf29f), each scored one at a time with overlay score <adopted source> --owner <owner> --span <regions.json span_bytes> on 8cb65f1: 150/152 differing_halfwords=0. The other two are resource_371:02002cb4 (1146 vs registered 1148) and resource_3a6:020011a0 (182 vs 184): both are exact through their final return, and the registered span includes the alignment halfword after it (the same shape as resource_378:0200290c, adopted 1930 inside its 1932 region), so they read dh=1 at the registered span and dh=0 at the adopted one. The registry spans are left as they were.