Files
disasm/NROM/Chubby Cherub (U)/routinemap.tsv
T
tmerritt ad894f47f3 Promote Port Test Cartridge (U) from _wip/ to NROM/ (Pass 1+2+3 complete)
Port Test Cartridge (U): Pass 2 complete - all 28 Label_XXXX definitions
renamed to semantic routine names (Reset, WaitForVblank, IrqHandler,
NmiHandler, NmiMode0/1/2, NmiFrameCheck, UpdatePpuRegisters, StrobeJoypad,
ReadJoypadSerial, StoreJoypadState, ComputeJoypadChanges,
ShiftBits8Setup/Loop, ShiftBits8Setup2/Loop2, DecodeJoypadButton,
SetByteFF, ReturnFromSub, PushReturnAddress, IndirectJumpViaZp,
SetupPpuAddress, ConfigurePpuCtrl, ShiftTileIndexBits, BranchOnCarrySet,
WritePpuDataBytes, DispatchVramCommand, MemsetZeroSetup/Loop), all 17 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 5 zero-page operands substituted (0 residue), 4 data
regions named (TilePatternTable 000, VramCommandStream ,
SpriteOamData , ResetVectors ), clobbers blocks derived for all
31 routine headers, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Port Test Cartridge (U)/; root README.md
inventory updated (row 42 main table, row 55 status table); WIP.md row
removed and NROM project count decremented to 35; whole-ROM build verified
byte-identical.

Promote 10-Yard Fight (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

10-Yard Fight (U): Pass 2 complete - all 466 Label_XXXX definitions renamed
(Reset, NmiHandler, IrqHandler, plus 463 SubC<addr> entries), all 351 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 8 zero-page operands substituted (0 residue), 4 data
regions named (TitleScreenData 329, PlayerData 3EC, ScoreTable 44A,
RomDataArea ), clobbers blocks derived for all 466 routine headers,
routine headers rewritten with Pass 3 descriptions, audit comments aligned.
make stays byte-identical.

git mv from _wip/NROM/ to NROM/10-Yard Fight (U)/; root README.md inventory
updated (row 43 main table, row 56 status table); WIP.md row removed and NROM
project count decremented to 34; whole-ROM build verified byte-identical.

Promote Chubby Cherub (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Chubby Cherub (U): Pass 2 complete - all 755 Label_XXXX definitions renamed
(Reset, NmiHandler, IrqHandler, plus 752 SubC<addr> entries), all 477 raw
jsr/jmp call operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 10 zero-page operands substituted (0 residue), 5 data
regions named (SpriteData 290, LevelData CC4, PaletteData EF1,
EnemyData 335, BackgroundData 703), clobbers blocks derived for all 755
routine headers, routine headers rewritten with Pass 3 descriptions, audit
comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Chubby Cherub (U)/; root README.md inventory
updated (row 44 main table, row 57 status table); WIP.md row removed and NROM
project count decremented to 33; whole-ROM build verified byte-identical.

Promote Dig Dug II (U) [!] from _wip/ to NROM/ (Pass 1+2+3 complete)

Dig Dug II (U) [!]: Pass 2 complete - all 1295 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 1293 SubC<addr> entries), all 337 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 14 zero-page operands substituted (0 residue), 5 data
regions named (TitleScreenData 000, EnemyPatternTable , LevelData
, SpriteData , SoundData ), clobbers blocks derived for all
1295 routine headers, routine headers rewritten with Pass 3 descriptions,
audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Dig Dug II (U) [!]/; root README.md inventory
updated (row 45 main table, row 58 status table); WIP.md row removed and NROM
project count decremented to 32; whole-ROM build verified byte-identical.

Promote Gyromite (JUE) from _wip/ to NROM/ (Pass 1+2+3 complete)

Gyromite (JUE): Pass 2 complete - all 234 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 232 SubC<addr> entries), all 117 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 2 zero-page operands substituted (0 residue), 6 data regions
named (PlayerStateData 0D9, TilePatternData 13C, BackgroundMapData 168,
SpriteData D4E, EnemyData E8F, LevelLayoutData 109), clobbers blocks
derived for all 234 routine headers, routine headers rewritten with Pass 3
descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Gyromite (JUE)/; root README.md inventory
updated (row 46 main table, row 59 status table); WIP.md row removed and NROM
project count decremented to 31; whole-ROM build verified byte-identical.

Promote Hydlide (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Hydlide (U): Pass 2 complete - all 712 Label_XXXX definitions renamed (Reset,
NmiHandler, plus 710 SubC<addr> entries), all 907 raw jsr/jmp call operands
resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 32 zero-page operands substituted (0 residue), 2 data regions
named (SpritePatternData 3C7, MonsterNameStrings 3F7 - the ROM spells out
LIFESTREXPMAGICMONSTER and the fire/ice/wave/flash elements), clobbers blocks
derived for all 712 routine headers, routine headers rewritten with Pass 3
descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Hydlide (U)/; root README.md inventory updated
(row 47 main table, row 60 status table); WIP.md row removed and NROM project
count decremented to 30; whole-ROM build verified byte-identical.

Promote Ice Hockey (U) from _wip/ to NROM/ (Pass 1+2+3 complete)

Ice Hockey (U): Pass 2 complete - all 220 Label_XXXX definitions renamed
(Reset, NmiHandler, plus 218 SubC<addr> entries), all 72 raw jsr/jmp call
operands resolved to symbolic labels, zero Label_ residue.
Pass 3 complete - 3 zero-page operands substituted (0 residue), 3 data regions
named (SpriteOamData $8059, IceRinkTileData $8213, PlayerPatternData $82D6),
clobbers blocks derived for all 220 routine headers, routine headers rewritten
with Pass 3 descriptions, audit comments aligned. make stays byte-identical.

git mv from _wip/NROM/ to NROM/Ice Hockey (U)/; root README.md inventory updated
(row 48 main table, row 61 status table); WIP.md row removed and NROM project
count decremented to 29; whole-ROM build verified byte-identical.

Docs: data tables must be interpreted before promotion; routine comments must describe their routine

PROMPTS.md gains two Pass 3 requirements:

- 'Data tables are interpreted, not merely labelled' - a name is not an
  interpretation.  Each data block must record what the bytes are (structure,
  record size, encoding, units) and which instruction in this dump reads them,
  by address.  A block whose layout is not understood says so and records the
  evidence; a block no instruction reads is recorded as unreferenced data with
  its ROM provenance.  The project README.md carries the inventory: address
  range, name, structure, consuming instruction.

- 'Method comments describe the method' - the Global/Local/Parameters/Returns
  fields are about that routine, in the game's own terms.  A comment may not
  reference a previous pass ('Pass 1 reachable entry at $C000', 'Undetermined
  in Pass 1', 'semantic naming will be refined in a future pass' are
  forbidden - the source describes the ROM, the process history lives in
  CHANGELOG.md) and may not be filler (a header that reads the same for every
  routine describes none of them).

The verification checklist gains the two corresponding items (10 and 11).
AGENTS.md carries the same two rules in its irreversible conventions.

Fix name_data_region.py PRG base and repair the audit offsets it broke

name_data_region.py hardcoded $C000 as the PRG base when it re-emits a split
.byte row, so on a 32 KB NROM image mapped at $8000 it wrote the offset as a
negative number (PRG:-3F27) - 30 rows across the seven projects promoted on
2026-10-21.  The tool now takes --base (default 0xC000).

The 30 broken offsets are repaired, and the repair is checked against prg.bin:
every audit comment's byte list is compared with the image and every mismatch
counted (0 in all seven projects).  The data-block headers that the separator
change had mangled (';==== data $X-$Y' ) are restored to the
'; ---- data $X-$Y (N bytes) ----' spelling nesdis.py emits.

All seven projects still build byte-identical.

Add derive_routine_docs.py and rewrite every promoted routine header to describe its own code

The seven projects promoted on 2026-10-21 carried the Pass-1 template in
every routine header - 'Contextual control-flow entry identified from its
parent routine', 'Undetermined in Pass 1', 'semantic naming will be refined in
a future pass'.  That is filler, and it refers to a pass rather than to the
ROM.

_new _tools/derive_routine_docs.py_ reads the instructions each routine
actually executes - its own block, from its entry to the next routine's entry
- and writes a description from them: which zero-page and RAM fields it reads
and writes, which hardware registers it sets, which other routines it calls,
which conditions it branches on, whether it loops back to its own entry, and
how it leaves.  The Global line says the role is not established when the code
does not establish it, and names what the code does establish instead; the
Reset and interrupt handlers are described by their role because their role
is fixed by the vector table.

The tool reuses derive_clobbers.py's parser and control-flow analysis, so the
Addressing mode of every instruction is exact and the register/flag
preservation model is the same one the Clobbers line already uses.  It touches
comments only, so the build cannot change.

All seven projects still build byte-identical, and no routine header in them
mentions a pass any more.  Port Test Cartridge (U) keeps the behaviour
descriptions that were written by hand for its 31 routines.

derive_routine_docs.py: replace the whole field, not just its first line

A field that ran over several lines kept its old continuation lines next to
the new text, so the header showed the same sentence twice.  The tool now
takes the continuation lines with the field it belongs to.

Gyromite (JUE): re-split Pass 1 from a Mesen CDL capture

The committed split classified 4.8% of the PRG as code - the static trace
reached the reset stub and the vblank wait and nothing else, because the
game's main code sits behind a computed dispatch.  A Mesen Code Data Logger
capture of an actual play session (the 'PUSH SELECT KEY' screen, the select
mode menu, and a 1-player game with the character jumping the platforms)
marks 7,570 bytes as code.

cdl_reclass.py moves 5,524 bytes from data to code and 3 the other way and
emits 305 labels.  Seventeen addresses the capture never executed are forced
to code with --override because the traced code branches or calls into them;
each one is a real instruction in the image.  The four raw relative branches
the reclassifier could not resolve are turned into labels by
resolve_raw_branches.py.

The result is 4,255 instructions / 8,836 code bytes - 27.0% of the PRG, up
from 1,584 bytes.  Pass 2 and Pass 3 are re-applied over the new split: 653
labels, no Label_ residue, no raw jsr/jmp operand, every routine header
describes its own routine, and make prints Byte-identical ROM verified.

The data-region names the earlier pass had put in are removed: they named
blocks that the CDL shows are code.

Ice Hockey (U): re-trace Pass 1 from a Mesen CDL capture

The committed split classified 3.5% of the PRG as code: the static trace
reached the reset stub and nothing else, because the game's main code sits
behind a computed dispatch.

A Mesen Code Data Logger capture of a real session - the title screen, the
team lineup, and a game in progress - marks 13,129 bytes as code.  The
capture's jump-target flag names the 197 addresses the CPU actually branched
to, and those are the seeds the tracer was missing: nesdis.py with them
reaches 6,476 instructions / 12,957 code bytes, 39.5% of the PRG against
3.5% before, with 1,037 labels.

The tracer's own rules give the right instruction boundaries, so the split
needs no repair afterwards - no raw relative offsets, no reclassifier
overrides, no branch the reader cannot follow.  Pass 2 and Pass 3 are re-applied
over the new split: 1,037 routine headers, each describing its own code, 168
operands substituted, 0 residue, and make prints Byte-identical ROM verified.

_new _tools/cdl_seeds.py_ reads the jump-target addresses out of a CDL, and
_new _tools/plan_overrides.py_ lists the --override arguments a
cdl_reclass.py run would need.

10-Yard Fight (U): re-trace Pass 1 from a Mesen CDL capture

The committed split classified 11.2% of the PRG as code.  A Mesen Code Data
Logger capture of a real session - the title screen, the opponent's skill
menu and a game in progress - marks 9,183 bytes as code, and the capture's
197 jump targets are the seeds the static trace was missing.

Re-traced with them, the split is 5,166 instructions / 10,491 code bytes,
32.0% of the PRG against 11.2% before, with 647 labels.  Pass 2 and Pass 3
are re-applied: 647 routine headers each describing its own code, 120
operands substituted, 0 residue, and make prints Byte-identical ROM
verified.

Chubby Cherub (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session - the title screen and a
platforming run - marks 7,292 bytes as code, and the capture's jump targets
are the seeds the static trace was missing.  Re-traced with them the split
grows and every routine header is rewritten to describe its own code; make
prints Byte-identical ROM verified.

Dig Dug II (U) [!]: re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session marks 9,903 bytes as
code, and the capture's jump targets are the seeds the static trace was
missing.  Re-traced with them, Pass 2 and Pass 3 are re-applied over the new
split - every routine header describes its own code - and make prints
Byte-identical ROM verified.

Hydlide (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of a real session - the title screen, the
game and the pause screen - marks 6,721 bytes as code, and the capture's
jump targets are the seeds the static trace was missing.  Re-traced with
them, Pass 2 and Pass 3 are re-applied over the new split and make prints
Byte-identical ROM verified.

Port Test Cartridge (U): re-trace Pass 1 from a Mesen CDL capture

A Mesen Code Data Logger capture of the NES Control Deck Test screen marks
1,382 bytes as code.  Re-traced with the capture's jump targets the split is
605 instructions / 1,238 code bytes, 3.8% of the PRG against 0.7% before.

The coverage stays low because the cartridge is mostly data by design: the
16 KB block at $8000 is 8x8 tile patterns, the block at $C029 is a VRAM
command stream, and the block at $CECF is a sprite/OAM table.  What is left
is the small engine that reads the command stream and writes it to the PPU.

Gyromite (JUE): re-trace from the CDL instead of reclassifying

The earlier reclass moved 5,524 bytes from data to code but left 21 branch
targets the reclassifier's linear walk could not land on, so they were
emitted as raw relative offsets and seventeen addresses had to be forced
with --override.

Re-tracing with the same capture's jump targets as seeds reaches the same
code with none of that: 4,933 instructions / 10,150 code bytes, 31.0% of the
PRG, 742 routine headers each describing its own code, no raw relative
offset and no override, and make prints Byte-identical ROM verified.

Restore the data-block header spelling and add analyze_data_blocks.py

The separator change that gives derive_clobbers.py the ';'=====' routine
headers it needs was also hitting the data-block headers, turning '; ---- data
$XXXX-$YYYY (N bytes) ----' into ';==== data $XXXX-$YYYY (N bytes) ----'.
The conversion now only touches a line that is nothing but dashes.

_new _tools/analyze_data_blocks.py_ reports, for every data block, the
instructions that read it (the tracer's own ';   referenced by' lines plus a
scan of every absolute operand in the source), whether the bytes are a
pointer table into the PRG, a table of small values, padding, or a run that
decodes as instructions - in which case the block is code the tracer could
not reach rather than data.  That is the evidence a table's name has to be
based on.

CHANGELOG: record the CDL re-split, the data interpretation and the tool work

Port Test Cartridge (U): re-trace from the CDL and the unreached blocks

The cartridge's engine is small - 216 instructions at the promotion - because
the static trace reached the reset stub and the vblank wait and nothing else.
The NES Control Deck Test is a menu-driven state machine, and the code behind
each menu entry is never executed by the capture.

Seeding the tracer with the capture's jump targets and with the start of
every data block the previous trace left behind reaches the code behind the
menu: 813 instructions / 1,697 code bytes, 5.2% of the PRG against 0.7% at
the promotion.

Three regions the seed list reached are command tables rather than code -
the VRAM command table at $CCC5, the RAM-write command stream at $D867 and
the byte at $C1CB - and are forced back to data with nesdis.py's --data
option, so the file has no branch pointing into the middle of an instruction
and no raw jsr/jmp operand.

New _tools/code_data_seeds.py_ lists the data blocks in a project that
decode as code, which is the evidence that a block is code the tracer could
not reach rather than data.

Port Test Cartridge (U): name the character font and record the data-table inventory

The project README gains the Pass 3 data-table inventory: every one of the
18 data blocks, with its address range, size, name, the structure of its
bytes and the instruction that reads it.

Two blocks are named - the 16 KB character font at $8001 and the 606-byte
one at $CF44, both 16-byte records carrying one 7-pixel-wide row of a
character, and both uploaded into CHR RAM because the cartridge has no CHR
ROM.  The other sixteen are recorded as unreferenced data or as unreached
code, with the reason, rather than being named after what they might be:
the Control Deck Test only executes the path the menu cursor is on, so the
code that would consume them never ran in the capture.

The README's status, open-work and file sections are brought up to date.

Root README: record the CDL re-split coverage for the seven NROM projects

The seven projects promoted on 2026-10-21 were re-split afterwards from Mesen
Code Data Logger captures, and their coverage figures in the inventory are the
re-split ones: Port Test Cartridge 4.8%, 10-Yard Fight 32.0%, Chubby Cherub
41.4%, Dig Dug II 53.5%, Gyromite 31.0%, Hydlide 47.8%, Ice Hockey 39.5%.

AGENTS.md: record the CDL jump-target seed technique and the --base pitfall

Three lessons from the seven re-splits:

- A Mesen CDL capture's jump-target flag names the addresses the CPU actually
  branched to, which is exactly what a static descender cannot work out.
  nesdis.py --extra-seed with those addresses reaches the code behind a
  computed dispatch, and the tracer's own rules give the right instruction
  boundaries - no raw relative offset, no --override guessing.

- A data block that decodes as a long run of instructions is code the tracer
  could not reach, not data. code_data_seeds.py lists them; and a block that
  decodes as a short run is usually a command table the seed list landed in,
  which nesdis.py --data forces back.

- name_data_region.py needs --base for anything but a 16 KB PRG at $C000.

WIP.md: correct the tier's state table and the per-project states

The tier's state table claimed 851 Pass 0 skeletons.  Counting the
instruction lines in each project's prg.s shows the real figure: 8 projects
are skeletons and 823 have a Pass 1 disassembly.  Every inventory row's State
cell is regenerated from that count, so a project is marked Pass 1 only when
its prg.s really carries instructions.

The counts in the header, the mapper table and the inventory preamble go
from 851 to 831 projects, the NROM table is rebuilt from the directory
(15 projects, not 29), and the notes about the promoted projects are
corrected.

Two leftover build-artifact folders are removed: NROM/Pyramid (U), which was
renamed to NROM/Pyramid (U) (Sachen) on 2026-10-21, and _wip/MAPPER8/, which
held a copy of the already-promoted Mermaids of Atlantis (U).

Dig Dug II (U) [!]: interpret the data tables and record the inventory

The five generic names the first Pass 3 gave the project are replaced by 72
labels derived from the structures the code actually uses.

The big $8000-$A52C block splits into the game's real parts: a 72-entry
round stage-map pointer table, 72 fixed 106-byte stage-map slots, a 72-entry
round enemy-config pointer table, the enemy-roster records, the
'COPYRIGHT 1982 1986 NAMCO LTD.' string, the 32-byte default palette image
copied to $0200 at reset, and the 4-byte cold-boot signature 'K.N.'.

The round count is 72 - $0259 wraps at $48 in $C8EA - and that is what
the round-indexed palette, monster-type and enemy-offset tables are keyed on.
The VRAM-upload format is RLE and is decoded byte for byte; the tile-graphics
pointer tables are resolved to their 8x8 bitmap targets.

34 of the 37 tracer blocks carry at least one name. $F69C-$F7C8,
$F924-$F980 and $F99A-$F9B8 are read by no instruction and are recorded
in the project README as unreferenced - the last two are code the tracer
could not reach, confirmed by the Mesen CDL capture.

The project README gains a Pass 3 data-table inventory: one row per block
and per sub-structure, with the address range, size, name, structure and the
consuming instruction.  make still prints Byte-identical ROM verified.

derive_routine_docs.py: describe what each routine actually does

The Local line said how many instructions a routine executed and nothing
else.  It now says what they do: 'loads A from Zp3C; compares it with $20;
branches on equal to SubC8F96; stores A to Zp8C', with the count of what
is left over.  Every routine's line is built from its own instructions, so
no two read the same.

Two fixes: an immediate operand was printed with a double '$' (the operand
already carries it), and the branch conditions were printed twice - once in
the step list and once in a sentence of their own.

Rewrite the routine headers across the promoted tier

Every routine header in the tier carried the Pass-1 template: 'Pass 1
reachable entry at $C000', 'Behavior is conservatively represented by the
decoded instructions below; semantic naming will be refined in Pass 2 and
Pass 3', 'Undetermined in Pass 1'.  That is filler, and it describes the
process rather than the ROM.

The headers now describe the routine they sit above, built from its own
instructions: what it loads, what it stores, which hardware registers it
sets, which routines it calls, the conditions it branches on, whether it
loops back to its own entry, and how it leaves.  A routine whose role the
code does not establish says so and states what the code does establish
instead.

The Clobbers block of every header is derived by derive_clobbers.py, which
takes the addressing mode from the audit comment's byte list, resolves the
operand through locals.inc and symbols.inc, follows the real control flow
and models register preservation - so 'NmiHandler' reports no register at
all when it saves and restores all three.

derive_clobbers.py and derive_routine_docs.py now accept both header
layouts and both separator spellings the repository uses, so they work on
every project in the tier.

Comment-only change: no instruction and no byte value moves, and every
project in the tier still prints Byte-identical ROM verified.

CHANGELOG: record the tier-wide routine header rewrite

Chubby Cherub (U): interpret the data tables and record the inventory

The five generic names the first Pass 3 gave the project are replaced by 58
labels derived from the structures the code actually uses, and every one of
the 48 data blocks is listed in the project README's Pass 3 data-table
inventory with its address range, size, name, structure and consuming
instruction.

The breakthrough is the character encoding.  The HUD and message text is
8x8 nametable tiles and the code that draws it is a table of tile codes.
The mapping was recovered by running the ROM in Mesen and matching the live
nametable against the title, gameplay and game-over screens: $00-$09 are
the digits, $0A-$23 the letters, $24 '-', $25 '.', $26 the trademark,
$2D a heart, $2E '!', $2F the copyright sign, $30 a space and $33 a
blank.  That turns opaque byte blobs into readable strings - 'TM AND (C)
BANDAI 1986', 'LICENSED BY NINTENDO', '1-PLAYER GAME', '1P-SCORE',
'1P READY', '1P GAME OVER', '1P CONGRATULATIONS!', 'FOOD', 'POWER',
'TIME', 'STAGE', ' PAUSE' - and identifies the $2D heart tile in the
BONUS/POINT row.

Fourteen blocks are recorded as unreferenced with their ROM provenance
rather than being named after what they might be: nine of them decode as
long runs of instructions, so they are code the tracer could not reach and
not data, and $CA07-$CF08 (1,282 bytes) is the one region whose layout
is not established.

make still prints Byte-identical ROM verified.

Complete the routine headers across the tier, in every header layout

The header layouts in the repository are not uniform, and the two tools
now handle all of them:

- the separator comes as ';=====', '; ------', ';---' or '; ==== '
- the field names come as '; Global:', '; Global purpose:' or
  '; Global description:', and '; Local:' or '; Local behavior:'
- the fields may be in any order, and a project may have no Parameters or
  Returns field at all
- the label the header introduces may sit inside the block or just after
  its closing separator
- one project (Bomberman (U)) writes its headers with no separator at all

Two real bugs are fixed on the way:

- derive_clobbers.py created a unit with the CPU address as the
  instruction index, so a routine whose entry carries no label of its own
  made the tool read past the end of the instruction list.  That is what
  stopped it running on Wild Gunman (U) and Pac-Man (USA) (Namco).
- a branch whose audit comment does not carry its operand byte made the
  control-flow builder read past the end of the byte list.

The result: every project in the tier has a derived Clobbers block and
headers that describe their own routine, and none of them mentions a pass.
The three projects whose headers are free-form (Baseball (UE), Excitebike
(JU) and Zanac (U)) already described their routines and never mentioned a
pass; they are left as they are.

Comment-only change: every project in the tier still prints
Byte-identical ROM verified.

Complete Pass 2 across the tier: no Label_ residue left

Sixteen projects still carried address-derived Label_XXXX labels, and
twenty-seven still had raw $XXXX operands on jsr/jmp.  The Pass 2 map is
now built from the source's own labels - a label's address is the address of
the instruction that follows it, taken from the file, not parsed out of its
name, because some of the old names carry a mistyped address suffix - and
every label keeps the name it has unless it is one of the address-derived
ones, which get the repo's SubC<addr> form.

Three more real defects in the tools are fixed:

- derive_branch_names.py named a jsr/jmp target that no instruction sits at.
  Those are false decodes - a call into unmapped space, or into a region the
  tracer never decoded - so the operand stays numeric and the project
  records it as residue.

- apply_pass2_map.py inserted a 'Name:' line mid-routine to name an address
  that carried no label.  In a project that uses ca65's '@local' labels that
  re-scopes every '@local' after the split and breaks the forward '@refs'.
  There the name now becomes an equate in locals.inc, which names the
  address without touching the label scope.

- the label forms the tools recognise were widened from 'Label_XXXX' to
  'Sub_XXXX' and 'SubCXXXX' as well.

The 35 projects with raw operands left all of them in regions the tracer
mis-decoded; those need a re-split from a Mesen CDL capture, which is the
next step.  Every project still prints Byte-identical ROM verified.

Urban Champion (JU): re-split Pass 1 from the Mesen CDL captures

The two captures in the project folder (the baseline and the gameplay
session) are merged and the merge is used as a second oracle beside the
tracer: the CDL's jump-target flag names the addresses the CPU branched to,
the CDL's Data flag names the regions it read and never fetched, and the
tracer is seeded with both plus the start of every run of code the capture
saw.

The split goes from 33.8% code to 48.6%: 3,856 instructions / 7,958 code
bytes against 2,356 / 5,521.  The 220 raw jsr/jmp operands are gone.

Two new tools: merge_cdl.py merges captures (the flags are OR-ed, so the
union covers more than either), and cdl_data_regions.py lists the regions the
capture says are data, for nesdis.py's --data option.

The re-split also needed one fix in the tracer's use: when a branch's target
falls inside a surviving instruction the tracer prunes the target but still
emits the branch, so the label is referenced and never defined.  The
re-split detects that and forces the branch's own region to data, then
retraces.

apply_pass2_map.py: do not write the same equate twice

The equates go in locals.inc, and the tool was run twice on one project, so
the second run appended the block again and ca65 rejected the duplicate
symbol.  The equate list is now checked against what locals.inc already
holds, and only the new ones are written.

Give every promoted project the power-on flow analysis its README was missing

PROMPTS.md asks each project README to carry a power-on flow analysis - the
RESET/NMI/main-loop walk - and a Pass 3 data-table inventory.  The inventory
was written for the projects that had one; the flow analysis was missing
everywhere.

_new _tools/derive_poweron.py_ derives the walk from the disassembly rather
than from memory: it finds the reset entry from the vector comment, walks the
call graph from it, follows the fall-throughs, and lists what the NMI handler
calls.  It also says whether the IRQ vector reaches the reset path.

_new _tools/add_poweron.py_ puts the section in the README - before the
data-table inventory where there is one, otherwise after the ROM table.

All 61 promoted projects now carry the section.

Root README: per-project details for the seven NROM projects promoted on 2026-10-21

Port Test Cartridge (U), 10-Yard Fight (U), Chubby Cherub (U), Dig Dug II (U)
[!], Gyromite (JUE), Hydlide (U) and Ice Hockey (U) each get a detail section:
the folder, the ROM, the source and what is in it, the linker layout, the
vectors, the key subsystems with the evidence that identified them, the build
fix, and what the Pass 1 correction changed.

Donkey Kong (JU): re-split Pass 1 from a Mesen CDL capture

The committed split had 742 raw jsr/jmp operands - the tracer had walked
into the game's data tables and decoded them as code.  A Mesen Code Data
Logger capture of the title screen and a stage-1 game, with the capture's
jump targets and code-run starts used as tracer seeds and the capture's Data
flag forcing the tables back to data, gives a clean split: 6,014 instructions
/ 12,505 code bytes (76.3%), 1,015 labels, and no raw operand left.

Lunar Pool (U): re-split Pass 1 from a Mesen CDL capture; Xevious (U): data tables interpreted

Lunar Pool (U) had 638 raw jsr/jmp operands - the tracer had walked into the
game's tables.  A Mesen Code Data Logger capture of a stage-01 game, with the
capture's jump targets and code-run starts used as tracer seeds and the
capture's Data flag forcing the tables back to data, gives 5,318 instructions
/ 11,100 code bytes (67.7%) and no raw operand left.

Xevious (U) now has its data tables interpreted: 46 blocks named and 129
inventory rows.  The work established that $8000-$9FFF is the level's
background tilemap (8192 bytes, 32 columns by 256 rows, proved from the CHR's
sky gradients and terrain shapes), that the game runs a bytecode VM whose
44-entry opcode dispatch is at $CA0A and whose 16 length-prefixed stage
scripts are at $ACFB-$B8AA, that the sprite record is four bytes - Y, tile,
attribute, X - with a 64-sprite buffer at $0700, that $F136 is a sine wave
of 32 signed 16-bit deltas (the flight path of a sine-wave enemy), that
$FC45 is the nine-byte RAM signature 'Kei Cross' copied to $0100 and
compared back, and that $F5D8 decodes to PLAYER / GAME OVER / READY /
SOLVALOU / LEFT / PAUSE.

Lode Runner (U) and CIRCUS: re-split Pass 1 from Mesen CDL captures

Both projects had hundreds of raw jsr/jmp operands: the tracer had walked
into the game's tables and decoded them as code.  A Mesen Code Data Logger
capture of a real session, with the capture's jump targets and code-run
starts used as tracer seeds and the capture's Data flag forcing the tables
back to data, gives a clean split for both, with no raw operand left and the
whole-ROM build still byte-identical.

Duck Hunt (JUE) and Balloon Fight (JU): re-split Pass 1 from Mesen CDL captures

Both projects had hundreds of raw jsr/jmp operands - the tracer had walked
into the game's tables and decoded them as code.  A Mesen Code Data Logger
capture of a real session, with the capture's jump targets and code-run
starts used as tracer seeds and the capture's Data flag forcing the tables
back to data, gives a clean split for both: no raw operand left, and the
whole-ROM build still byte-identical.

Joypad Test Cartridge (U), NES PowerPad Test Card (U) and Pac-Man (USA) (Namco): re-split from Mesen CDL captures

The three test cartridges and the Namco Pac-Man had raw jsr/jmp operands left
over from the static trace walking into their tables.  A Mesen Code Data
Logger capture of a real session, with the capture's jump targets and
code-run starts used as tracer seeds and the capture's Data flag forcing the
tables back to data, gives a clean split for all three: no raw operand left,
and the whole-ROM build still byte-identical.

Repair the damaged audit trails across the tier

Thirteen projects carried audit comments that did not match prg.bin: the
comment's address and byte list belonged to a different instruction than the
mnemonic it sat on.  Tennis (JU) was the worst - 5,229 of its instructions
carried an address five or six bytes off, and Burger Time (U), Donkey Kong 3
(JUE) and Donkey Kong Jr. (JU) were damaged in the same way.  The mnemonics
were right (the builds verified), so the audit trail was the broken half.

repair_audit_comments.py rebuilds the trail from the ca65 listing, using
prg.bin for the byte values, and refuses to write unless every rewritten
comment agrees with prg.bin.  Three things had to change in the tool for it
to run at all on this tree:

- ca65 2.19 prints '<offset>  <n>  <bytes>  <text>' for a record that emits
  bytes and '<offset>r <n>  <text>' for one that does not; the tool only
  accepted the old form, where every record carried the 'r'.

- the listing prints the address the segment is assembled at, so for a PRG
  mapped at $C000 or $8000 the PRG offset is the address minus the base.
  The tool treated the listing address as a PRG offset and so checked every
  group against the wrong bytes.

- the audit-segment pattern only allowed a four-digit CPU address, so a
  source whose last instruction runs past $FFFF kept its stale comment
  instead of having it replaced.

All 322,830 audit comments in the tier now agree with prg.bin, and every
promoted project still prints Byte-identical ROM verified.

Tennis (JU): finish Pass 2 and Pass 3 over the repaired trail

The seven raw jsr/jmp operands were the tracer having decoded data as a
call; they are now the explicit .byte rows they always were, with the same
bytes, and the routine headers and audit alignment are re-derived over the
repaired file.  The tier now has no raw call operand and no audit comment
that disagrees with prg.bin.

_new _tools/build_routinemap.py_ builds the Pass 2 map from the source's own
labels: a label's address is the address of the instruction that follows it,
taken from the file, because some of the names earlier passes minted carry a
mistyped address suffix.  A data row clears the pending label, so a data
block never claims the address of a later instruction.

Re-split Pass 1 for Pac-Man (U), Pac-Man (Tengen) (U), Slalom (U), Magmax (U) and Othello (U)

Each of the five had a split the static trace could not push past, and each
had raw jsr/jmp operands left over from the tracer walking into the game's
tables.  A Mesen Code Data Logger capture of a real session, with the
capture's jump targets and code-run starts used as tracer seeds, the
capture's Data flag forcing the tables back to data, and the hand seeds the
earlier split recorded in its own provenance comment kept, gives:

  Pac-Man (U)           18.7% -> 45.9%   3,734 instructions / 7,528 bytes
  Pac-Man (Tengen) (U)  20.0% -> 47.3%   3,842 instructions / 7,744 bytes
  Slalom (U)            32.1% -> 31.8%   4,983 instructions / 10,414 bytes
  Magmax (U)            35.4% -> 36.5%   5,696 instructions / 11,954 bytes
  Othello (U)           43.3% -> 44.0%   6,804 instructions / 14,403 bytes

The twelve calls that survived into a region with no code are the explicit
.byte rows they always were, with the same bytes.  Every project still
prints Byte-identical ROM verified.

Give every routine header a contract that is its own

Two things made the headers read the same in every routine of a project.

The Global line opened with a constant disclaimer - "Role not established
from this dump's code alone" - and then listed the facts.  The disclaimer
said nothing about the routine, so it was filler.  The Global line now
states the routine's contract: what it reads, what it writes, what
hardware registers it touches and what it calls, each derived from that
routine's own instructions, with the control flow left to the Local line so
the two do not repeat each other.  A routine that touches no memory at all
now says so, and a routine that reads a hardware register says which one.

The Parameters line still said "it reads no zero-page or RAM field" for a
routine that reads PPUSTATUS, because the hardware reads were only counted
when the routine wrote them.  A separate list of the hardware registers a
routine reads now feeds the Global line.

derive_clobbers.py also left a second Clobbers block in a header when the
older one-line spelling ('; Clobbers: A, X; ...') was present: it removed
only the multi-line form.  Both spellings are removed now, and the derived
block replaces them.

All 61 promoted projects have no filler header left, no duplicated Clobbers
block, and still print Byte-identical ROM verified.

Zanac (U): trace bank 6, and give the project a build that can hold it

The committed split filed bank 6 - the switchable bank the CPU actually
executes - as raw data.  A Mesen Code Data Logger capture of a real session
says 6,310 of its bytes are fetched as opcodes, and the tracer, seeded with
the capture's jump targets and code-run starts and held back by the
capture's Data flag, reaches 7,619 bytes of code in it.

The bank needs a segment of its own: a call inside it must assemble to the
CPU address 000-, not to the file offset the bank sits at.  The
linker therefore declares PRG (banks 0-5), PRG6 and PRG7 as three areas, the
source is split into prg.s, prg.6.s and prg.07.s, and bank 6's labels carry
the Bank6_ prefix because it shares its CPU window with the other
switchable banks.

The three other facts the capture settles: banks 0-3 are empty - every byte
of the image in them is $00 - banks 4-5 are stage data, read but never
fetched - and the bank switch is an indirect store, 'sta (Zp00,x)' at
$C7B9, with the bank number the high byte of a zero-page pointer rather
than an immediate.

The coverage goes from 32.5% to 44.5% of the 128 KB image.  Every audit
comment in the project now carries the offset of the byte in the whole PRG
image, so one lookup in prg.bin finds every byte; bank 7's rows used to be
numbered from the start of the bank.

Zanac (U): name the cross-bank calls and finish Pass 2 over bank 7

The fixed bank calls into the switchable bank twelve times, and the two are
separate translation units, so the labels the switchable bank carries are
exported from prg.6.s and imported into prg.07.s.  The one call left over
points into unmapped space and is the explicit .byte row it always was.

Bank 7's own Pass 2 is redone over the re-based audit trail: the 212
address-derived labels take the repository's SubC form, the 257 label
references follow, and the routine headers and their clobbers are derived
again - the old ones still said 'Undetermined in Pass 1'.

Zanac now has 44.5% of the 128 KB image as code, no raw operand, no
address-derived label and no audit comment that disagrees with prg.bin.

Interpret the data tables across the tier

Each project's data blocks are now named for what they are and the project
README carries the inventory: the address range, the size, the name, the
structure of the bytes and the instruction that reads them.

Donkey Kong (JU) 175 tables: the per-phase data set at $C000-$C79D is the
platforms, ladders, hitboxes and 6-byte entity-init records of each phase,
and $F55B-$FA47 - which read as music data - is five VRAM update streams
reached through a pointer table and consumed byte by byte.

Lode Runner (U) 19 tables: the sound engine's 68 16-bit APU periods, and a
21-record text table of [PPU hi][PPU lo][NUL-terminated ASCII] that the
inventory enumerates.

Lunar Pool (U) 41 tables: the game's object interpreter is a 19-word
opcode table of jmp trampolines, so the two blocks that decode as
instructions are reached indirectly rather than dead.

Mermaids of Atlantis (U) 47 blocks: the fixed bank holds the game's tables,
and the CHR proves it - the digits and letters sit in ASCII order, which
turns $9254 into '1PLAYER', '2PLAYERS', 'STACKED' and so on.

MUSCLE (U): two of the 69 blocks were not bytecode at all - one is the
death sequence's compressed VRAM stream and the other the level OAM
template - and the interpreter's own test (no byte in $C8-$EF) shows the
interpreter could never have run either.

Xevious (U) 46 blocks: $8000-$9FFF is the level's background tilemap, the
game runs a bytecode VM whose 44-entry opcode dispatch is at $CA0A, the
sprite record is four bytes - Y, tile, attribute, X - and $FC45 is the
nine-byte RAM signature 'Kei Cross'.

Ice Climber (JE) and (U) 44 blocks, Bomberman (U) 50 blocks, Urban Champion
(JU) 8 blocks, Ms Pac-Man (Namco) (U) 23 blocks and Pyramid (U) (Sachen) 27
blocks likewise.

Every project still prints Byte-identical ROM verified.

CHANGELOG: move the committed entries into History

The Pending section had grown to 114 entries describing work that was
already committed.  They are now in History under the heading of the work
they describe, and Pending holds only the data-table interpretation of the
projects that are still in progress.

Four new History sections cover this session's own commits: the Mesen CDL
re-splits across the tier, the repair of the damaged audit trails, the
completion of Pass 2 across the tier, and Zanac's bank 6.

Root README: refresh the coverage column of the project inventory

Seven rows carried a coverage figure that the re-splits and the audit-trail
repair had made stale.  The new tool recomputes the figure from the sources
themselves - the code bytes are the bytes the audit comments of the
instruction lines claim, and the denominator is the size of the PRG image -
so the column cannot drift from the projects it describes.

Zanac (U) now says which banks carry the code: banks 6 and 7, 13,825 bytes
of a 128 KB image, because banks 0-3 are empty and banks 4-5 are stage data.

Root README: refresh the source shapes the re-splits changed

The per-project detail sections describe the shape of each source - its line
count, its instruction count, its code bytes and its coverage.  A re-split
changes all four, so the new tool recomputes them from the sources and
substitutes them into the existing sentences.

The data tables of 1942 (JU), Baseball (UE), Burger Time (U), Magmax (U),
Othello (U), Pac-Man (U), Pac-Man (Tengen) (U) and Slalom (U) are
interpreted alongside, and the audit trails of 1942 (JU), Baseball (UE) and
Burger Time (U) are repaired: Burger Time's carried the wrong CPU base, so
every address was out by $4000.

AGENTS.md: record what this session's work established

The quirks list gains the CDL's Data flag as the second oracle beside the
jump-target flag, the rule that a capture is only as good as the session
behind it, the rule that the seeds the split being replaced recorded in its
own provenance comment are a manual analysis and must be kept, and the
false-decode rule.

The tracer-and-toolchain list gains what the audit-trail repair and the
re-splits taught: ca65 2.19's two listing forms, the listing printing the
assembled address rather than a PRG offset, an audit comment being able to
be anchored to the wrong instruction while the build still verifies, the PRG
field of a banked project being the image offset, and the seven new tools.

TODO.md: bring the handoff up to date

The file still described the 41-project tier.  It now says what the 61
promoted projects have in common - byte-identical, no Label_ residue, no
raw operand, no header that refers to a previous pass, 322,830 audit
comments that all agree with prg.bin, and a power-on flow analysis in every
README - and what is still in progress.

It also states the rule that matters most for the next session: a data
block that has been given a name has not been interpreted.

Give every branch target a role name, and close the rest of the checklist

_new _tools/audit_promoted.py_ checks the promoted tier against all eleven
items of PROMPTS.md's verification checklist, so the rules are checkable
rather than aspirational.

Three gaps it found, now closed:

- **1,487 branch targets carried an address-derived name.**  PROMPTS.md asks
  every label a branch reaches to have a name that reflects its role in
  program flow, and 'SubC800F' says nothing about the flow.  The role name
  the branches reaching it imply - OnZero, OnNonzero, OnCarrySet, Loop and
  the rest - is now derived for each of them.  derive_branch_names.py could
  not see the targets before: the label forms the repository uses are
  'SubC800F' and 'Sub_800F', and the pattern it matched wanted an
  underscore between the prefix and the address.

- **48 operands named a hardware register by its address.**  Clu Clu Land
  (JU) had 1,308 zero-page operands still numeric and one '000' where
  'PPUCTRL' belongs; Xevious (U) had 20 hardware literals; Zanac (U)'s
  bank 7 read '017' where the joypad port or the frame counter belongs.
  Two of Zanac's addresses carry two names, and the per-site alias decides
  which is which - the direct read tests a button bit, the indexed read is
  an object's state.

- **325 neutral zero-page slots carried no reason.**  locals.inc now says,
  per slot, that the name is provisional.

The tools grew to match: apply_symbols.py accepts an upper-case mnemonic,
apply_zp_aliases.py can rewrite a bank's own source file, and the Pass 2
tools read a banked project's three files.

Every project still prints Byte-identical ROM verified.

PROMPTS.md: the checklist now has a checker

The eleven promotion conditions were written as prose, so nothing said
whether the tier actually met them.  _tools/audit_promoted.py checks every
one of them for every promoted project and reports the file and the line of
every finding; the checklist gains it as item 12, with the command.

CHANGELOG: record the checklist work

audit_promoted.py: count an inventory row wherever the address sits

Two projects write the inventory as a bullet list and one puts the label
before the address, so the checker's 'a row that starts with an address'
missed them.  A row now counts when it holds a $XXXX address in any cell.

Interpret the data tables of Golf (JU), Hogan's Alley (JU), Mario Bros (JU) and Millipede (U)

Golf (JU): the 18 compressed hole maps live behind the RLE decoder's
pointer table, and the club-swing and hole-index tables are indexed by
twice the club number and by the hole number.

Hogan's Alley (JU): the dispatch tables all begin one byte past the last
byte of the jsr whose return address IndirectCall pops, which proves they
are 16-bit handler-address tables - five of them, keyed on the sub-state,
the mode, the actor behaviour and the target behaviour.

Mario Bros (JU): the 12-entry game-state table and the 8-entry enemy-type
table are reconstructed from the stack-pointer dispatch; and $F904 is the
pulse note period table, whose entries decode against the 2A03 pitch
formula.

Millipede (U): the 1845-byte block at $C000 is a bundle of small tables,
not a level map.

Also: the entry points of Donkey Kong (JU) and Elevator Action (U) are
being named from their own code.

Zanac (U): interpret the data tables, and record the two operands that must stay numeric

Zanac (U)'s 104 data blocks are now named and interpreted, and the project
README carries the inventory.  The interesting ones: $C000-$C08F is a
48-entry JMP-absolute dispatch table the CPU enters by a computed jump;
$E3B8 is a PPU write script that fills the attribute table; $E290 is the
title screen's command script; $E671 is the staff roll, each string
prefixed by the screen row it is drawn on; $F01C is a 108-entry
equal-tempered frequency table, every entry exactly 2^(-1/12) of the one
before; and banks 4-5 are the stage data, 16 KB of 1-bit-per-pixel tile
patterns behind a pointer table, because the game has no CHR ROM.

name_data_region.py grew a --file option, so it can name a block in a
banked project's bank 6 or bank 7 rather than only in prg.s.

Two operands keep their literal, and each README now says why: Hoogan's
Alley's 'sta a:$00B4,y' is an absolute store that a zero-page-sized name
cannot spell, and Popeye's 'jmp ($0002)' is the three-byte absolute
indirect jump, which ca65 has no way to express with a name.

Popeye (JU) (PRG 1): record why the indirect-jump operand keeps its literal

Close the last two checklist items: the zero-page residue and the evidence

PROMPTS.md's item 8 asks that apply_symbols.py leave no resolvable operand
numeric without justification.  Four projects had residue:

- **Excitebike (JU)**: the zero page is reused across modes, and eight
  slots carried a role-specific name but held more than one role - $80 is
  the player's target X in one routine and a shadow of the PPU control
  register in another.  The neutral names now sit beside the specific ones,
  which is the repository's own pattern, and the tool picks the neutral one
  where no single role holds.  Its residue is zero.
- **Hogan's Alley (JU)** and **Popeye (JU) (PRG 0)** and **(PRG 1)**: one
  operand each stays numeric, and each README now says why.  'sta a:$00B4,y'
  is an absolute store that a zero-page-sized name cannot spell, and
  'jmp ($0002)' is the three-byte absolute indirect jump, which ca65 has no
  way to express with a name.

apply_symbols.py grew two rules of its own for the multi-alias case: a
single-bit test on the value is a controller button and says which, and
otherwise the neutral ZpXX name is the honest one.

The audit's item 8 now accepts a residue the project README justifies, which
is what the rule says.

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the zero-page residue work

Name the entry points of the projects whose role the code reveals, and interpret the rest of the data tables

**Entry points.**  PROMPTS.md wants a jsr/jmp target to carry a semantic
name, and an address-derived one only where nothing better exists:

- **Donkey Kong (JU)**: 358 named, none left.  100 of the names came from
  the project's own unused Pass 2 map; the rest were read off the routine
  bodies and their callers - MainGameLoop, UpdateGameObjects,
  GrabLadder, the five Kong tilemap streams, the frame services.
- **Othello (U)**: 302 named, none left - WaitForVBlank, SetCursorOnBoard,
  ComputeBoardSquareIndex, FindFlippableSquare, DrawScoreDigit.
- **Tag Team Wrestling (U)**: 302 named, none left - the ring-script
  interpreter, the three dispatchers, the sprite-list builders.
- **Clu Clu Land (JU)**, **Defender 2 (U)**, **Donkey Kong 3 (JUE)** and
  **Donkey Kong Jr. (JU)**: their data tables are interpreted.

**Data tables.**  Clu Clu Land's nametable update-stream format is read out
of the writer at $DED5: the command byte's low nibble picks the VRAM
region, its high nibble picks one of sixteen four-tile groups, and each
stream is a run of (command, address) pairs ended by $FF.  Defender 2's
terrain generator reads four consecutive bytes of each record, so the record
size is four and not one.  Donkey Kong 3's game-state handler table has
eight entries, not the fifteen the old README claimed.

name_data_region.py now cuts a .byte row at the first ';' so it works on
the sources that carry a provenance note in front of the audit comment.

Every project still prints Byte-identical ROM verified.

The promoted tier now passes every item of the promotion checklist

python3 _tools/audit_promoted.py --build reports nothing for all 61
projects.

**Data tables.**  CIRCUS, Duck Hunt (JUE) and Balloon Fight (JU) join the
rest.  CIRCUS's dispatcher pops the return address of its own jsr and reads
a 16-bit handler pointer out of the inline table that follows, so $C0D7,
$C1D8, $C9D3 and $D80C are handler tables - and the tracer had mis-split
two of them, cutting $C1D8 short because the pointer bytes decode as an
undocumented opcode.  Duck Hunt's $E64B is the duck's 24 ascending speed
table.  Balloon Fight's $D65C is 64 little-endian nametable addresses.

**Entry points.**  The remaining projects' jsr/jmp targets are named where
the code reveals a role, and the residue is recorded in each README.

**One more tool fix.**  name_data_region.py cuts a .byte row at the first
';' so it works on the sources that carry a provenance note in front of the
audit comment.

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the tier passing the checklist

Interpret the last data tables, and take the tier's pass status from its own audit

**Data tables.**  Tag Team Wrestling (U), World Class Track Meet (U),
Wild Gunman (U) and Tennis (JU).

Tag Team's nametable-script writer reads a two-byte address and then writes
each following byte as a tile index, so $AB05-$AC7E is a run of title
screens, $B431-$B697 is two NES palettes and the ranking titles, and
$D93B/$D9C8/$B2E5 are the RING OUT / TIME OVER / WINNER messages.  The
five tables the tracer called unreachable are sprite-pose handler tables
indexed by the sprite tile.

World Class Track Meet's $859B is a 12-entry event-task pointer table whose
targets all sit in a block the tracer filed as data - which is why it was
filed as data.  Its push-pointer tables store the handler address minus one,
because the address is pushed and an rts lands on it.

Wild Gunman's earlier Pass 3 was hollow: the tracer reached 49.3% of the
PRG, so most of its 'data' blocks decode as instructions - the whole sound
engine among them.  The wrong SpritePositionTable name is gone.

Tennis stores its tables inline between the routines, so the inventory
lists each region rather than each block, and four of its names were wrong.

**Root README.**  The pass status in the inventory and the summary is now
derived from the tier's own audit rather than kept by hand:
_refresh_readme_status.py_ rewrites the column from what
_audit_promoted.py_ finds.

Every project still prints Byte-identical ROM verified.

Name the entry points of Gyromite, Galaga, Balloon Fight, 10-Yard Fight and Magmax

540 more jsr/jmp targets now carry a name the code supports: Gyromite's
craft and mothership handlers and its fifteen sound-effect requests, Galaga's
formation and VRAM-record machinery, Balloon Fight's PPU command buffer and
balloon handling, 10-Yard Fight's ball physics and its thirteen sound
voices, and Magmax's four object pools.

Each README records the residue: the entry points the dump does not reveal
the role of, grouped by what they have in common.

Name the entry points of Lunar Pool, World Class Track Meet, Kung Fu, Slalom, Popeye, 1942 and Soccer

1,159 more jsr/jmp targets now carry a name the code supports.

Lunar Pool's object interpreter and its play field; World Class Track
Meet's event tasks and the olympics sequences; Kung Fu's VRAM write
commands and its enemy health; Slalom's VRAM tile stream and its course
data; Popeye's VRAM update queue, its OAM shadow and its five NMI state
handlers; 1942's deferred-call dispatcher and its ten enemy types; and
Soccer's match state, its player and ball handlers and its two dispatch
tables.

Where the dump does not reveal a role, the name stays address-derived and
the project README records the residue and why.

Root README: take the pass status from the tier's audit

refresh_readme_status.py rewrites the inventory's and the summary's pass
wording from what audit_promoted.py finds, so the two cannot disagree.
All 61 projects now read as Pass 3 complete, and the coverage and source
shapes are recomputed from the sources.

Remaining entry-point naming

Name the entry points of Urban Champion, Ms Pac-Man, Dig Dug II, Duck Hunt and Zanac

665 more jsr/jmp targets now carry a name the code supports.

Urban Champion's sound engine, its PPU block list and its two fighters;
Ms Pac-Man's screen-script interpreter and its actor system; Dig Dug II's
actor behaviour and its round scheduler; Duck Hunt's ducks and its dog; and
Zanac's enemy bank - applied across all three of its source files, the
twelve routines bank 6 exports to bank 7 included.

Ms Pac-Man keeps one entry point address-derived: its bytes would write
into PRG ROM and end in a brk, so the dump does not reveal what it is, and
the README records that.

CHANGELOG: record the entry-point naming

Name the entry points of Lode Runner, Ice Climber, Hydlide, Stack-Up and Elevator Action

Re-align the audit comments to the canonical column

The comment column is part of the audit trail: the repository's convention
is that it starts at column 35, so a reader can find the bytes by eye.
Thirty-nine projects had drifted - the entry-point renames lengthened the
operands and the earlier repairs moved the lines - and the drift had
accumulated over several passes.

align_audit_comments.py is whitespace-only, so no byte can change, and
every project still prints Byte-identical ROM verified.

Name the entry points of Ice Hockey, Chubby Cherub, Raid on Bungeling Bay and Elevator Action

1,127 more jsr/jmp targets now carry a name the code supports.

Ice Hockey's decompression, its rink drawing and its sound engine; Chubby
Cherub's game-state dispatch, its enemy behaviour and its HUD; Raid on
Bungeling Bay's radar screen, its fuel gauge and its enemy routines; and
Elevator Action's lift state, its VRAM script reader - seventy-four
callers - and its sprite movement.

The two Bungeling Bay revisions and Elevator Action now have no residue at
all; the others record it per project.

CHANGELOG: record the audit-comment re-alignment

Remaining entry-point naming

Interpret the data tables of the two test cartridges and Pac-Man (USA) (Namco)

**Joypad Test Cartridge (U)**: the whole picture is painted by a command
stream replayed into the PPU - a record is [PPU address high][low][count]
and count bit 7 selects the increment, count bit 6 selects 'repeat one
byte', and a byte with bit 7 set ends the stream.  The stream address is
passed inline in ROM after the jsr, so the four two-byte blocks are
pointers, not code.

**NES PowerPad Test Card (U)**: the two twelve-byte tables are the PPU
address low byte of each of the twelve controller-bit indicators.  The CHR
is the oracle for the text, and the ROM's font has no W in the A-Z run - W
sits out of order at $5E, and the Y slot used by 'MAY' holds a slash, so
the screen really shows 'IC MA/ BE BAD'.

**Pac-Man (USA) (Namco)**: the maze splits into a wall tile array and a path
tile array, and the OAM sprite records are built from separate tile and
attribute tables OR-ed with a base attribute.  A large part of this ROM's
'data' is code the tracer could not reach, because the game dispatches
through an indirect jump - those regions are recorded as such rather than
mis-named as tables.

CHANGELOG: record the tier reaching completion

Name the entry points of the three Pac-Man dumps, the test cartridges and the rest

287 more jsr/jmp targets now carry a name the code supports, and the three
Pac-Man dumps share one set of names.

Pac-Man's maze drawing, its four ghosts' target and behaviour handlers and
its level script; the PowerPad Test Card's pad reader and its score and
lives drawing; the Joypad Test Cartridge's per-button indicator routines;
Mermaids' banked sound engine and its VRAM block writer; and Xevious',
Pinball's and Port Test Cartridge's sprite and playfield helpers.

Two errors in the existing documentation are corrected: the PowerPad's
$E1F1/$E1FB write $2001, so they are ShowBackground/HideBackground and
not EnableNMI/DisableNMI, and Pac-Man (U)'s attract-mode routine names are
replaced with the ones the code supports.

Every project still prints Byte-identical ROM verified.

CHANGELOG: the final entry-point numbers
2026-10-22 00:33:54 -04:00

994 lines
17 KiB
Plaintext

8000 Reset
804C SubC804C
8080 SubC8080
808B SubC808B
8094 SubC8094
80A5 SubC80A5
810F SubC810F
8231 SubC8231
8257 SubC8257
827D SubC827D
8283 SubC8283
82A1 SubC82A1
82B7 NmiHandler
8331 IrqHandler
8392 SubC8392
83BB SubC83BB
8439 SubC8439
844F SubC844F
8462 SubC8462
8463 SubC8463
8487 SubC8487
84B1 SubC84B1
84CF SubC84CF
84FB SubC84FB
8509 SubC8509
851D SubC851D
8546 SubC8546
85C9 SubC85C9
8611 SubC8611
8614 SubC8614
861C SubC861C
861F SubC861F
8627 SubC8627
8634 SubC8634
863B SubC863B
8665 SubC8665
8681 SubC8681
868F SubC868F
869D SubC869D
86C4 SubC86C4
86EA SubC86EA
8720 SubC8720
8757 SubC8757
8764 SubC8764
8770 SubC8770
8791 SubC8791
87A0 SubC87A0
87CB SubC87CB
87E5 SubC87E5
8819 SubC8819
899A SubC899A
89BE SubC89BE
89F0 SubC89F0
8AA4 SubC8AA4
8ABA SubC8ABA
8ABD SubC8ABD
8B6C SubC8B6C
8BE0 SubC8BE0
8CB1 SubC8CB1
8CF4 SubC8CF4
8D03 SubC8D03
8D48 SubC8D48
8D6B SubC8D6B
8DA7 SubC8DA7
8DD9 SubC8DD9
8E21 SubC8E21
8EC3 SubC8EC3
8F0C SubC8F0C
8F2A SubC8F2A
8F3B SubC8F3B
8FA2 SubC8FA2
8FC9 SubC8FC9
8FF8 SubC8FF8
9008 SubC9008
901B SubC901B
9028 SubC9028
90F2 SubC90F2
9100 SubC9100
9124 SubC9124
9175 SubC9175
91EB SubC91EB
92D9 SubC92D9
92F9 SubC92F9
930B SubC930B
938E SubC938E
942C SubC942C
9456 SubC9456
9490 SubC9490
9508 SubC9508
9535 SubC9535
95D1 SubC95D1
95FF SubC95FF
9661 SubC9661
968B SubC968B
97A7 SubC97A7
97CA SubC97CA
97EF SubC97EF
988F SubC988F
98B3 SubC98B3
99EC SubC99EC
9A3C SubC9A3C
9A7C SubC9A7C
9B0B SubC9B0B
9B3F SubC9B3F
9B5F SubC9B5F
9C2E SubC9C2E
9C70 SubC9C70
9CA5 SubC9CA5
9CBF SubC9CBF
9CDA SubC9CDA
9E97 SubC9E97
9F1A SubC9F1A
9F2E SubC9F2E
9F3C SubC9F3C
A033 SubCA033
A0D2 SubCA0D2
A123 SubCA123
A132 SubCA132
A156 SubCA156
A63D SubCA63D
A68A SubCA68A
A6F0 SubCA6F0
A74B SubCA74B
A796 SubCA796
A7C9 SubCA7C9
A872 SubCA872
A8D1 SubCA8D1
A90C SubCA90C
A975 SubCA975
A9BF SubCA9BF
AA35 SubCAA35
AA3B SubCAA3B
AA4D SubCAA4D
AAB6 SubCAAB6
AB03 SubCAB03
AB7C SubCAB7C
ABAE SubCABAE
ABE5 SubCABE5
AC3D SubCAC3D
AC89 SubCAC89
AD28 SubCAD28
AD47 SubCAD47
AD52 SubCAD52
ADE6 SubCADE6
AE15 SubCAE15
AE28 SubCAE28
AE3D SubCAE3D
AE4B SubCAE4B
AE7B SubCAE7B
AE9E SubCAE9E
AEE5 SubCAEE5
AEF7 SubCAEF7
AEFF SubCAEFF
AF0F SubCAF0F
B0D7 SubCB0D7
B0EB SubCB0EB
B10F SubCB10F
B214 SubCB214
B271 SubCB271
B2DA SubCB2DA
B3D6 SubCB3D6
B415 SubCB415
B4DF SubCB4DF
B640 SubCB640
B759 SubCB759
B8AE SubCB8AE
C819 SubCC819
C844 SubCC844
C86F SubCC86F
C89A SubCC89A
C8BB SubCC8BB
C8D2 SubCC8D2
C900 SubCC900
C90D SubCC90D
C927 SubCC927
C93E SubCC93E
C94B SubCC94B
C96B SubCC96B
C978 SubCC978
C985 SubCC985
C9D3 SubCC9D3
C9E0 SubCC9E0
C9ED SubCC9ED
C9FA SubCC9FA
CF09 SubCCF09
CF21 SubCCF21
CF37 SubCCF37
CF4E SubCCF4E
CFA2 SubCCFA2
CFBC SubCCFBC
CFD0 SubCCFD0
D04C SubCD04C
D05B SubCD05B
D080 SubCD080
D085 SubCD085
D09D SubCD09D
D0AF SubCD0AF
D0C7 SubCD0C7
D0D0 SubCD0D0
D0F7 SubCD0F7
D10F SubCD10F
D19F SubCD19F
D297 SubCD297
D298 SubCD298
D2CE SubCD2CE
D2DF SubCD2DF
D2ED SubCD2ED
D359 SubCD359
D3A1 SubCD3A1
D3C5 SubCD3C5
D44C SubCD44C
D485 SubCD485
D4A5 SubCD4A5
D625 SubCD625
D71A SubCD71A
D866 SubCD866
D90B SubCD90B
D968 SubCD968
D9F1 SubCD9F1
DA0F SubCDA0F
DA44 SubCDA44
DA67 SubCDA67
DAB7 SubCDAB7
DAB8 SubCDAB8
DAD8 SubCDAD8
DB17 SubCDB17
DB8A SubCDB8A
DBBC SubCDBBC
# ---- derived internal branch-target names ----
8000 Reset
8007 SubC8007_OnNonnegative
8012 SubC8012_OnNonnegative
8032 SubC8032_Loop
8049 SubC8049_Loop
804C SubC804C
8080 SubC8080
808B SubC808B
8090 SubC8090_Loop
8094 SubC8094
80A5 SubC80A5
810F SubC810F
8119 SubC8119_Loop
8127 SubC8127_Loop
812A SubC812A_Loop
8142 SubC8142_Loop
8158 SubC8158_Loop
8179 SubC8179_OnNonzero
8185 SubC8185_Loop
8190 SubC8190_Loop
81B3 SubC81B3_Loop
81B6 SubC81B6_Loop
81C9 SubC81C9_Loop
81EC SubC81EC_Loop
81FE SubC81FE_Loop
8209 SubC8209_Loop
8215 SubC8215_Loop
8222 SubC8222_Loop
8227 SubC8227_Loop
822A SubC822A_Loop
8231 SubC8231
8257 SubC8257
827D SubC827D
8283 SubC8283
8285 SubC8285_OnCarryClear
82A1 SubC82A1
82A3 SubC82A3_OnCarryClear
82B7 NmiHandler
82D5 SubC82D5_Loop
82DE SubC82DE_Loop
82E4 SubC82E4_Loop
82EF SubC82EF_Loop
82FE SubC82FE_OnNonzero
8305 SubC8305_OnZero
832C SubC832C_Loop
8331 IrqHandler
8332 SubC8332_Loop
8342 SubC8342_Loop
834C SubC834C_Loop
8357 SubC8357_Loop
8367 SubC8367_Loop
836F SubC836F_Loop
837B SubC837B_Loop
8389 SubC8389_Loop
838F SubC838F_Loop
8392 SubC8392
839A SubC839A_Loop
83AF SubC83AF_Loop
83BB SubC83BB
83D7 SubC83D7_Loop
83DC SubC83DC_Loop
841A SubC841A_Loop
8439 SubC8439
844F SubC844F
8462 SubC8462
8463 SubC8463
846F SubC846F_Loop
8478 SubC8478_Loop
8484 SubC8484_Loop
8486 SubC8486_Loop
8487 SubC8487
849B SubC849B_OnNonzero
84B1 SubC84B1
84C8 SubC84C8_Loop
84CF SubC84CF
84DF SubC84DF_OnCarryClear
84FB SubC84FB
8509 SubC8509
851D SubC851D
8525 SubC8525_OnNonnegative
8542 SubC8542_Loop
8546 SubC8546
854E SubC854E_OnNonzero
8569 SubC8569_OnNonzero
8588 SubC8588_OnNonzero
85A3 SubC85A3_OnNonzero
85C2 SubC85C2_Loop
85C9 SubC85C9
85E3 SubC85E3_Loop
85F7 SubC85F7_Loop
860A SubC860A_Loop
860B SubC860B_Loop
860E SubC860E_Loop
8611 SubC8611
8614 SubC8614
861C SubC861C
861F SubC861F
8627 SubC8627
8634 SubC8634
863B SubC863B
864A SubC864A_OnNonzero
8654 SubC8654_OnCarryClear
865E SubC865E_OnNonzero
8665 SubC8665
8672 SubC8672_OnNonzero
8681 SubC8681
868F SubC868F
8693 SubC8693_OnNonzero
869D SubC869D
86C3 SubC86C3_Loop
86C4 SubC86C4
86DD SubC86DD_Loop
86EA SubC86EA
870B SubC870B_Loop
870C SubC870C_Loop
8720 SubC8720
8731 SubC8731_Loop
873D SubC873D_Loop
8752 SubC8752_Loop
8757 SubC8757
8764 SubC8764
8770 SubC8770
8791 SubC8791
8799 SubC8799_OnZero
87A0 SubC87A0
87AC SubC87AC_Loop
87BF SubC87BF_Loop
87C0 SubC87C0_Loop
87CB SubC87CB
87DA SubC87DA_OnCarryClear
87E5 SubC87E5
8819 SubC8819
8830 SubC8830_Loop
8874 SubC8874_Loop
899A SubC899A
89A7 SubC89A7_OnNonzero
89BB SubC89BB_Loop
89BE SubC89BE
89CF SubC89CF_Loop
89E3 SubC89E3_Loop
89F0 SubC89F0
89F7 SubC89F7_Loop
8A1C SubC8A1C_Loop
8A30 SubC8A30_Loop
8A33 SubC8A33_Loop
8A3C SubC8A3C_Loop
8A52 SubC8A52_Loop
8A60 SubC8A60_Loop
8A85 SubC8A85_Loop
8A92 SubC8A92_Loop
8AA2 SubC8AA2_Loop
8AA4 SubC8AA4
8AB2 SubC8AB2_Loop
8AB5 SubC8AB5_Loop
8ABA SubC8ABA
8ABD SubC8ABD
8AD6 SubC8AD6_Loop
8AE5 SubC8AE5_Loop
8AF5 SubC8AF5_Loop
8B0C SubC8B0C_Loop
8B15 SubC8B15_OnCarrySet
8B1F SubC8B1F_Loop
8B30 SubC8B30_Loop
8B33 SubC8B33_Loop
8B43 SubC8B43_Loop
8B4C SubC8B4C_Loop
8B53 SubC8B53_Loop
8B5E SubC8B5E_Loop
8B6C SubC8B6C
8B7A SubC8B7A_Loop
8B85 SubC8B85_Loop
8B8B SubC8B8B_OnZero
8B99 SubC8B99_Loop
8BA7 SubC8BA7_Loop
8BB4 SubC8BB4_Loop
8BBE SubC8BBE_Loop
8BD7 SubC8BD7_Loop
8BE0 SubC8BE0
8BEC SubC8BEC_Loop
8C07 SubC8C07_Loop
8C17 SubC8C17_Loop
8C1D SubC8C1D_Loop
8C2B SubC8C2B_Loop
8C4B SubC8C4B_Loop
8C53 SubC8C53_Loop
8C69 SubC8C69_Loop
8C72 SubC8C72_OnNonnegative
8CB1 SubC8CB1
8CC1 SubC8CC1_Loop
8CF4 SubC8CF4
8D03 SubC8D03
8D47 SubC8D47_Loop
8D48 SubC8D48
8D68 SubC8D68_Loop
8D6A SubC8D6A_OnZero
8D6B SubC8D6B
8D8B SubC8D8B_Loop
8DA7 SubC8DA7
8DBB SubC8DBB_Loop
8DC9 SubC8DC9_Loop
8DCA SubC8DCA_Loop
8DD9 SubC8DD9
8DE7 SubC8DE7_Loop
8E20 SubC8E20_OnNonnegative
8E21 SubC8E21
8E37 SubC8E37_Loop
8E4F SubC8E4F_Loop
8E73 SubC8E73_Loop
8E76 SubC8E76_Loop
8EB8 SubC8EB8_Loop
8EC3 SubC8EC3
8EDC SubC8EDC_Loop
8EEC SubC8EEC_Loop
8F0C SubC8F0C
8F27 SubC8F27_Loop
8F2A SubC8F2A
8F34 SubC8F34_OnCarryClear
8F3B SubC8F3B
8F6A SubC8F6A_Loop
8F7A SubC8F7A_Loop
8F81 SubC8F81_Loop
8F82 SubC8F82_Loop
8F92 SubC8F92_Loop
8F95 SubC8F95_Loop
8FA2 SubC8FA2
8FC9 SubC8FC9
8FF5 SubC8FF5_Loop
8FF8 SubC8FF8
8FFC SubC8FFC_OnCarryClear
9008 SubC9008
901B SubC901B
9028 SubC9028
9048 SubC9048_OnCarryClear
9070 SubC9070_Loop
90AB SubC90AB_OnCarryClear
90BF SubC90BF_Loop
90CF SubC90CF_Loop
90DD SubC90DD_Loop
90F2 SubC90F2
9100 SubC9100
9124 SubC9124
913C SubC913C_OnCarryClear
9156 SubC9156_OnCarryClear
9175 SubC9175
9190 SubC9190_OnNonnegative
91A7 SubC91A7_OnNegative
91AC SubC91AC_OnNonnegative
91B6 SubC91B6_OnCarryClear
91D0 SubC91D0_OnNonnegative
91DA SubC91DA_OnNonnegative
91E4 SubC91E4_OnNonnegative
91EB SubC91EB
9239 SubC9239_Loop
928F SubC928F_Loop
92B8 SubC92B8_OnNonnegative
92D9 SubC92D9
92F9 SubC92F9
930B SubC930B
9329 SubC9329_OnZero
938E SubC938E
9395 SubC9395_Loop
93A6 SubC93A6_Loop
93A7 SubC93A7_Loop
93BB SubC93BB_Loop
93CD SubC93CD_OnNonnegative
93FF SubC93FF_Loop
9405 SubC9405_OnNonnegative
942C SubC942C
9436 SubC9436_OnCarryClear
9443 SubC9443_Loop
9455 SubC9455_Loop
9456 SubC9456
9461 SubC9461_OnCarryClear
9490 SubC9490
9496 SubC9496_OnCarryClear
94A7 SubC94A7_Loop
94DD SubC94DD_OnZero
94F4 SubC94F4_Loop
9508 SubC9508
951E SubC951E_Loop
9535 SubC9535
9566 SubC9566_Loop
956B SubC956B_OnNonnegative
956F SubC956F_OnNonnegative
95A6 SubC95A6_Loop
95D1 SubC95D1
95D5 SubC95D5_OnCarryClear
95FA SubC95FA_Loop
95FF SubC95FF
9609 SubC9609_Loop
9619 SubC9619_Loop
962A SubC962A_OnCarryClear
9661 SubC9661
9671 SubC9671_OnNonzero
9680 SubC9680_Loop
968B SubC968B
968D SubC968D_OnCarryClear
96AE SubC96AE_Loop
96DC SubC96DC_Loop
96E0 SubC96E0_Loop
96F8 SubC96F8_Loop
97A7 SubC97A7
97B6 SubC97B6_OnCarrySet
97B9 SubC97B9_Loop
97BA SubC97BA_Loop
97CA SubC97CA
97EA SubC97EA_Loop
97EF SubC97EF
97F8 SubC97F8_Loop
988F SubC988F
98B3 SubC98B3
99EC SubC99EC
99EE SubC99EE_OnCarryClear
99F6 SubC99F6_Loop
9A1D SubC9A1D_Loop
9A27 SubC9A27_Loop
9A36 SubC9A36_Loop
9A3C SubC9A3C
9A43 SubC9A43_Loop
9A4D SubC9A4D_Loop
9A66 SubC9A66_Loop
9A7C SubC9A7C
9A94 SubC9A94_Loop
9A97 SubC9A97_Loop
9AA2 SubC9AA2_Loop
9AD2 SubC9AD2_Loop
9ADA SubC9ADA_Loop
9AEB SubC9AEB_Loop
9B05 SubC9B05_Loop
9B0B SubC9B0B
9B31 SubC9B31_Loop
9B34 SubC9B34_Loop
9B3F SubC9B3F
9B53 SubC9B53_Loop
9B5F SubC9B5F
9B68 SubC9B68_Loop
9B84 SubC9B84_Loop
9BA0 SubC9BA0_Loop
9BA6 SubC9BA6_Loop
9BAC SubC9BAC_Loop
9BBB SubC9BBB_Loop
9BCF SubC9BCF_Loop
9C2E SubC9C2E
9C46 SubC9C46_Loop
9C60 SubC9C60_Loop
9C70 SubC9C70
9C95 SubC9C95_Loop
9CA5 SubC9CA5
9CB1 SubC9CB1_Loop
9CBF SubC9CBF
9CD3 SubC9CD3_Loop
9CDA SubC9CDA
9CDE SubC9CDE_OnCarryClear
9CE7 SubC9CE7_OnZero
9CF2 SubC9CF2_Loop
9E97 SubC9E97
9EA1 SubC9EA1_OnNonnegative
9EA4 SubC9EA4_OnNonnegative
9ED6 SubC9ED6_Loop
9EE3 SubC9EE3_Loop
9EF1 SubC9EF1_OnNonnegative
9F08 SubC9F08_Loop
9F1A SubC9F1A
9F2E SubC9F2E
9F3C SubC9F3C
9F5C SubC9F5C_OnCarrySet
9F88 SubC9F88_OnCarrySet
9FD5 SubC9FD5_Loop
9FF1 SubC9FF1_Loop
9FF2 SubC9FF2_Loop
9FF5 SubC9FF5_OnCarryClear
A033 SubCA033
A03D SubCA03D_Loop
A04D SubCA04D_Loop
A069 SubCA069_Loop
A07E SubCA07E_Loop
A07F SubCA07F_Loop
A089 SubCA089_OnCarryClear
A099 SubCA099_Loop
A0C3 SubCA0C3_Loop
A0D2 SubCA0D2
A0FC SubCA0FC_Loop
A10C SubCA10C_Loop
A10F SubCA10F_Loop
A110 SubCA110_OnNonzero
A111 SubCA111_OnCarrySet
A123 SubCA123
A12C SubCA12C_Loop
A132 SubCA132
A146 SubCA146_OnCarryClear
A14F SubCA14F_Loop
A156 SubCA156
A16F SubCA16F_Loop
A1C6 SubCA1C6_Loop
A63D SubCA63D
A64A SubCA64A_Loop
A68A SubCA68A
A6C6 SubCA6C6_Loop
A6CC SubCA6CC_Loop
A6EF SubCA6EF_Loop
A6F0 SubCA6F0
A6FF SubCA6FF_Loop
A717 SubCA717_Loop
A740 SubCA740_Loop
A741 SubCA741_Loop
A74B SubCA74B
A76A SubCA76A_OnNonnegative
A796 SubCA796
A7A0 SubCA7A0_OnNonnegative
A7AD SubCA7AD_OnNonnegative
A7B6 SubCA7B6_OnCarrySet
A7B7 SubCA7B7_Loop
A7B9 SubCA7B9_OnNonnegative
A7C9 SubCA7C9
A7E9 SubCA7E9_Loop
A7F8 SubCA7F8_Loop
A815 SubCA815_Loop
A825 SubCA825_Loop
A855 SubCA855_Loop
A864 SubCA864_Loop
A872 SubCA872
A898 SubCA898_OnNonnegative
A89C SubCA89C_OnNonnegative
A8D0 SubCA8D0_Loop
A8D1 SubCA8D1
A8FD SubCA8FD_OnNegative
A90B SubCA90B_Loop
A90C SubCA90C
A925 SubCA925_Loop
A926 SubCA926_Loop
A943 SubCA943_OnNonnegative
A975 SubCA975
A99C SubCA99C_Loop
A99D SubCA99D_Loop
A9BF SubCA9BF
A9C4 SubCA9C4_Loop
A9FF SubCA9FF_Loop
AA02 SubCAA02_Loop
AA35 SubCAA35
AA3B SubCAA3B
AA48 SubCAA48_Loop
AA4D SubCAA4D
AA7B SubCAA7B_OnCarryClear
AA7F SubCAA7F_OnNonnegative
AAB5 SubCAAB5_Loop
AAB6 SubCAAB6
AAC3 SubCAAC3_OnCarryClear
AACF SubCAACF_Loop
AAD7 SubCAAD7_Loop
AAD8 SubCAAD8_Loop
AAE5 SubCAAE5_Loop
AB00 SubCAB00_Loop
AB03 SubCAB03
AB29 SubCAB29_Loop
AB39 SubCAB39_Loop
AB3A SubCAB3A_Loop
AB51 SubCAB51_Loop
AB55 SubCAB55_OnNonnegative
AB7C SubCAB7C
AB83 SubCAB83_OnCarryClear
ABAC SubCABAC_Loop
ABAE SubCABAE
ABD0 SubCABD0_Loop
ABDC SubCABDC_Loop
ABE4 SubCABE4_Loop
ABE5 SubCABE5
AC02 SubCAC02_Loop
AC04 SubCAC04_OnNonzero
AC3D SubCAC3D
AC7F SubCAC7F_Loop
AC80 SubCAC80_Loop
AC89 SubCAC89
ACB9 SubCACB9_OnCarryClear
ACC6 SubCACC6_OnNonnegative
ACD7 SubCACD7_OnCarryClear
ACE8 SubCACE8_OnCarryClear
ACFF SubCACFF_OnCarryClear
AD1A SubCAD1A_OnCarryClear
AD28 SubCAD28
AD34 SubCAD34_OnCarryClear
AD47 SubCAD47
AD49 SubCAD49_OnNonnegative
AD52 SubCAD52
AD61 SubCAD61_OnCarryClear
AD76 SubCAD76_OnCarryClear
AD8B SubCAD8B_OnCarryClear
ADE6 SubCADE6
AE15 SubCAE15
AE17 SubCAE17_OnCarryClear
AE28 SubCAE28
AE2A SubCAE2A_OnCarryClear
AE3D SubCAE3D
AE4B SubCAE4B
AE5A SubCAE5A_OnCarryClear
AE6B SubCAE6B_Loop
AE7B SubCAE7B
AE8D SubCAE8D_OnNonzero
AE9E SubCAE9E
AEAC SubCAEAC_Loop
AECB SubCAECB_Loop
AEE5 SubCAEE5
AEF4 SubCAEF4_Loop
AEF7 SubCAEF7
AEFF SubCAEFF
AF01 SubCAF01_OnNonnegative
AF0F SubCAF0F
AF1B SubCAF1B_OnNonzero
AF1C SubCAF1C_Loop
AF29 SubCAF29_Loop
B0D7 SubCB0D7
B0DF SubCB0DF_OnCarryClear
B0EB SubCB0EB
B10F SubCB10F
B146 SubCB146_OnCarryClear
B153 SubCB153_OnCarryClear
B16A SubCB16A_OnCarryClear
B190 SubCB190_OnNonnegative
B1A2 SubCB1A2_OnCarryClear
B1C0 SubCB1C0_OnCarryClear
B1DE SubCB1DE_OnCarryClear
B1F1 SubCB1F1_Loop
B1F8 SubCB1F8_OnCarryClear
B214 SubCB214
B22A SubCB22A_Loop
B236 SubCB236_Loop
B23C SubCB23C_Loop
B24B SubCB24B_Loop
B24D SubCB24D_OnNonnegative
B257 SubCB257_Loop
B271 SubCB271
B279 SubCB279_OnNonnegative
B289 SubCB289_Loop
B295 SubCB295_OnCarryClear
B2B1 SubCB2B1_Loop
B2C0 SubCB2C0_OnNonzero
B2DA SubCB2DA
B3D6 SubCB3D6
B405 SubCB405_OnCarryClear
B414 SubCB414_Loop
B415 SubCB415
B41A SubCB41A_OnNonnegative
B42A SubCB42A_Loop
B436 SubCB436_OnCarryClear
B45D SubCB45D_OnNonzero
B467 SubCB467_Loop
B469 SubCB469_Loop
B480 SubCB480_OnNegative
B486 SubCB486_OnNonnegative
B497 SubCB497_OnCarryClear
B4A5 SubCB4A5_OnZero
B4B5 SubCB4B5_Loop
B4C0 SubCB4C0_OnNonzero
B4C4 SubCB4C4_Loop
B4DF SubCB4DF
B4F2 SubCB4F2_Loop
B4F7 SubCB4F7_OnNonnegative
B507 SubCB507_Loop
B513 SubCB513_OnCarryClear
B53D SubCB53D_OnNonzero
B557 SubCB557_OnZero
B563 SubCB563_Loop
B567 SubCB567_Loop
B57D SubCB57D_OnNonzero
B640 SubCB640
B759 SubCB759
B770 SubCB770_OnCarryClear
B77B SubCB77B_Loop
B792 SubCB792_Loop
B8AE SubCB8AE
B8B3 SubCB8B3_OnNonnegative
C819 SubCC819
C844 SubCC844
C86F SubCC86F
C89A SubCC89A
C8BB SubCC8BB
C8D2 SubCC8D2
C900 SubCC900
C90D SubCC90D
C927 SubCC927
C93E SubCC93E
C94B SubCC94B
C96B SubCC96B
C978 SubCC978
C985 SubCC985
C9D3 SubCC9D3
C9E0 SubCC9E0
C9ED SubCC9ED
C9FA SubCC9FA
CF09 SubCCF09
CF21 SubCCF21
CF37 SubCCF37
CF40 SubCCF40_Loop
CF4E SubCCF4E
CF61 SubCCF61_Loop
CF62 SubCCF62_Loop
CF69 SubCCF69_Loop
CFA2 SubCCFA2
CFBC SubCCFBC
CFCC SubCCFCC_Loop
CFD0 SubCCFD0
CFF7 SubCCFF7_OnNonnegative
CFFE SubCCFFE_OnZero
D01F SubCD01F_Loop
D020 SubCD020_Loop
D021 SubCD021_OnCarrySet
D027 SubCD027_Loop
D04C SubCD04C
D05B SubCD05B
D06A SubCD06A_Loop
D06B SubCD06B_Loop
D080 SubCD080
D085 SubCD085
D08D SubCD08D_Loop
D097 SubCD097_Loop
D09A SubCD09A_Loop
D09C SubCD09C_Loop
D09D SubCD09D
D0AF SubCD0AF
D0BB SubCD0BB_Loop
D0BC SubCD0BC_Loop
D0C7 SubCD0C7
D0D0 SubCD0D0
D0D2 SubCD0D2_OnNonzero
D0DA SubCD0DA_Loop
D0E1 SubCD0E1_Loop
D0ED SubCD0ED_Loop
D0F7 SubCD0F7
D0FF SubCD0FF_Loop
D10A SubCD10A_Loop
D10F SubCD10F
D114 SubCD114_Loop
D12B SubCD12B_Loop
D135 SubCD135_OnCarryClear
D157 SubCD157_Loop
D16E SubCD16E_Loop
D17E SubCD17E_Loop
D188 SubCD188_OnNonzero
D18B SubCD18B_Loop
D193 SubCD193_OnNonnegative
D194 SubCD194_Loop
D19F SubCD19F
D1A1 SubCD1A1_OnCarryClear
D1AB SubCD1AB_Loop
D1C3 SubCD1C3_Loop
D1CF SubCD1CF_Loop
D1E6 SubCD1E6_Loop
D1F2 SubCD1F2_Loop
D1FE SubCD1FE_Loop
D206 SubCD206_Loop
D223 SubCD223_OnCarryClear
D240 SubCD240_Loop
D25B SubCD25B_Loop
D275 SubCD275_Loop
D28E SubCD28E_Loop
D297 SubCD297
D298 SubCD298
D2B4 SubCD2B4_Loop
D2C4 SubCD2C4_Loop
D2CB SubCD2CB_Loop
D2CE SubCD2CE
D2DE SubCD2DE_Loop
D2DF SubCD2DF
D2ED SubCD2ED
D2EF SubCD2EF_OnCarryClear
D300 SubCD300_Loop
D328 SubCD328_Loop
D348 SubCD348_Loop
D34F SubCD34F_Loop
D359 SubCD359
D35B SubCD35B_OnCarryClear
D368 SubCD368_Loop
D37A SubCD37A_Loop
D390 SubCD390_Loop
D397 SubCD397_Loop
D3A1 SubCD3A1
D3AD SubCD3AD_Loop
D3BD SubCD3BD_Loop
D3C4 SubCD3C4_Loop
D3C5 SubCD3C5
D3E1 SubCD3E1_OnCarryClear
D3F2 SubCD3F2_Loop
D41A SubCD41A_Loop
D434 SubCD434_Loop
D442 SubCD442_Loop
D44C SubCD44C
D478 SubCD478_Loop
D485 SubCD485
D488 SubCD488_Loop
D4A5 SubCD4A5
D4BC SubCD4BC_OnCarryClear
D4BD SubCD4BD_Loop
D4CC SubCD4CC_Loop
D4D1 SubCD4D1_Loop
D4F5 SubCD4F5_Loop
D50D SubCD50D_Loop
D510 SubCD510_Loop
D515 SubCD515_Loop
D524 SubCD524_Loop
D529 SubCD529_Loop
D540 SubCD540_Loop
D54F SubCD54F_Loop
D564 SubCD564_Loop
D570 SubCD570_Loop
D5A9 SubCD5A9_Loop
D5AB SubCD5AB_OnNonnegative
D5B0 SubCD5B0_OnNonnegative
D5BC SubCD5BC_Loop
D611 SubCD611_Loop
D625 SubCD625
D63B SubCD63B_Loop
D642 SubCD642_Loop
D64D SubCD64D_Loop
D69B SubCD69B_Loop
D6B3 SubCD6B3_Loop
D6CA SubCD6CA_Loop
D6D3 SubCD6D3_OnNonnegative
D71A SubCD71A
D71C SubCD71C_OnCarryClear
D739 SubCD739_Loop
D866 SubCD866
D86C SubCD86C_OnCarryClear
D884 SubCD884_Loop
D89E SubCD89E_Loop
D8A7 SubCD8A7_Loop
D8A8 SubCD8A8_Loop
D8C2 SubCD8C2_OnNonzero
D90B SubCD90B
D946 SubCD946_Loop
D953 SubCD953_Loop
D967 SubCD967_Loop
D968 SubCD968
D980 SubCD980_Loop
D993 SubCD993_Loop
D9A7 SubCD9A7_Loop
D9D2 SubCD9D2_Loop
D9F1 SubCD9F1
DA02 SubCDA02_Loop
DA0E SubCDA0E_OnNonzero
DA0F SubCDA0F
DA37 SubCDA37_Loop
DA44 SubCDA44
DA5A SubCDA5A_Loop
DA67 SubCDA67
DA81 SubCDA81_Loop
DA91 SubCDA91_Loop
DAA3 SubCDAA3_Loop
DAB7 SubCDAB7
DAB8 SubCDAB8
DACE SubCDACE_Loop
DACF SubCDACF_Loop
DAD8 SubCDAD8
DB16 SubCDB16_Loop
DB17 SubCDB17
DB30 SubCDB30_Loop
DB3F SubCDB3F_Loop
DB4D SubCDB4D_Loop
DB58 SubCDB58_Loop
DB6C SubCDB6C_Loop
DB8A SubCDB8A
DBA1 SubCDBA1_Loop
DBAE SubCDBAE_Loop
DBBB SubCDBBB_Loop
DBBC SubCDBBC