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

17 KiB

18000Reset
2804CSubC804C
38080SubC8080
4808BSubC808B
58094SubC8094
680A5SubC80A5
7810FSubC810F
88231SubC8231
98257SubC8257
10827DSubC827D
118283SubC8283
1282A1SubC82A1
1382B7NmiHandler
148331IrqHandler
158392SubC8392
1683BBSubC83BB
178439SubC8439
18844FSubC844F
198462SubC8462
208463SubC8463
218487SubC8487
2284B1SubC84B1
2384CFSubC84CF
2484FBSubC84FB
258509SubC8509
26851DSubC851D
278546SubC8546
2885C9SubC85C9
298611SubC8611
308614SubC8614
31861CSubC861C
32861FSubC861F
338627SubC8627
348634SubC8634
35863BSubC863B
368665SubC8665
378681SubC8681
38868FSubC868F
39869DSubC869D
4086C4SubC86C4
4186EASubC86EA
428720SubC8720
438757SubC8757
448764SubC8764
458770SubC8770
468791SubC8791
4787A0SubC87A0
4887CBSubC87CB
4987E5SubC87E5
508819SubC8819
51899ASubC899A
5289BESubC89BE
5389F0SubC89F0
548AA4SubC8AA4
558ABASubC8ABA
568ABDSubC8ABD
578B6CSubC8B6C
588BE0SubC8BE0
598CB1SubC8CB1
608CF4SubC8CF4
618D03SubC8D03
628D48SubC8D48
638D6BSubC8D6B
648DA7SubC8DA7
658DD9SubC8DD9
668E21SubC8E21
678EC3SubC8EC3
688F0CSubC8F0C
698F2ASubC8F2A
708F3BSubC8F3B
718FA2SubC8FA2
728FC9SubC8FC9
738FF8SubC8FF8
749008SubC9008
75901BSubC901B
769028SubC9028
7790F2SubC90F2
789100SubC9100
799124SubC9124
809175SubC9175
8191EBSubC91EB
8292D9SubC92D9
8392F9SubC92F9
84930BSubC930B
85938ESubC938E
86942CSubC942C
879456SubC9456
889490SubC9490
899508SubC9508
909535SubC9535
9195D1SubC95D1
9295FFSubC95FF
939661SubC9661
94968BSubC968B
9597A7SubC97A7
9697CASubC97CA
9797EFSubC97EF
98988FSubC988F
9998B3SubC98B3
10099ECSubC99EC
1019A3CSubC9A3C
1029A7CSubC9A7C
1039B0BSubC9B0B
1049B3FSubC9B3F
1059B5FSubC9B5F
1069C2ESubC9C2E
1079C70SubC9C70
1089CA5SubC9CA5
1099CBFSubC9CBF
1109CDASubC9CDA
1119E97SubC9E97
1129F1ASubC9F1A
1139F2ESubC9F2E
1149F3CSubC9F3C
115A033SubCA033
116A0D2SubCA0D2
117A123SubCA123
118A132SubCA132
119A156SubCA156
120A63DSubCA63D
121A68ASubCA68A
122A6F0SubCA6F0
123A74BSubCA74B
124A796SubCA796
125A7C9SubCA7C9
126A872SubCA872
127A8D1SubCA8D1
128A90CSubCA90C
129A975SubCA975
130A9BFSubCA9BF
131AA35SubCAA35
132AA3BSubCAA3B
133AA4DSubCAA4D
134AAB6SubCAAB6
135AB03SubCAB03
136AB7CSubCAB7C
137ABAESubCABAE
138ABE5SubCABE5
139AC3DSubCAC3D
140AC89SubCAC89
141AD28SubCAD28
142AD47SubCAD47
143AD52SubCAD52
144ADE6SubCADE6
145AE15SubCAE15
146AE28SubCAE28
147AE3DSubCAE3D
148AE4BSubCAE4B
149AE7BSubCAE7B
150AE9ESubCAE9E
151AEE5SubCAEE5
152AEF7SubCAEF7
153AEFFSubCAEFF
154AF0FSubCAF0F
155B0D7SubCB0D7
156B0EBSubCB0EB
157B10FSubCB10F
158B214SubCB214
159B271SubCB271
160B2DASubCB2DA
161B3D6SubCB3D6
162B415SubCB415
163B4DFSubCB4DF
164B640SubCB640
165B759SubCB759
166B8AESubCB8AE
167C819SubCC819
168C844SubCC844
169C86FSubCC86F
170C89ASubCC89A
171C8BBSubCC8BB
172C8D2SubCC8D2
173C900SubCC900
174C90DSubCC90D
175C927SubCC927
176C93ESubCC93E
177C94BSubCC94B
178C96BSubCC96B
179C978SubCC978
180C985SubCC985
181C9D3SubCC9D3
182C9E0SubCC9E0
183C9EDSubCC9ED
184C9FASubCC9FA
185CF09SubCCF09
186CF21SubCCF21
187CF37SubCCF37
188CF4ESubCCF4E
189CFA2SubCCFA2
190CFBCSubCCFBC
191CFD0SubCCFD0
192D04CSubCD04C
193D05BSubCD05B
194D080SubCD080
195D085SubCD085
196D09DSubCD09D
197D0AFSubCD0AF
198D0C7SubCD0C7
199D0D0SubCD0D0
200D0F7SubCD0F7
201D10FSubCD10F
202D19FSubCD19F
203D297SubCD297
204D298SubCD298
205D2CESubCD2CE
206D2DFSubCD2DF
207D2EDSubCD2ED
208D359SubCD359
209D3A1SubCD3A1
210D3C5SubCD3C5
211D44CSubCD44C
212D485SubCD485
213D4A5SubCD4A5
214D625SubCD625
215D71ASubCD71A
216D866SubCD866
217D90BSubCD90B
218D968SubCD968
219D9F1SubCD9F1
220DA0FSubCDA0F
221DA44SubCDA44
222DA67SubCDA67
223DAB7SubCDAB7
224DAB8SubCDAB8
225DAD8SubCDAD8
226DB17SubCDB17
227DB8ASubCDB8A
228DBBCSubCDBBC
229# ---- derived internal branch-target names ----
2308000Reset
2318007SubC8007_OnNonnegative
2328012SubC8012_OnNonnegative
2338032SubC8032_Loop
2348049SubC8049_Loop
235804CSubC804C
2368080SubC8080
237808BSubC808B
2388090SubC8090_Loop
2398094SubC8094
24080A5SubC80A5
241810FSubC810F
2428119SubC8119_Loop
2438127SubC8127_Loop
244812ASubC812A_Loop
2458142SubC8142_Loop
2468158SubC8158_Loop
2478179SubC8179_OnNonzero
2488185SubC8185_Loop
2498190SubC8190_Loop
25081B3SubC81B3_Loop
25181B6SubC81B6_Loop
25281C9SubC81C9_Loop
25381ECSubC81EC_Loop
25481FESubC81FE_Loop
2558209SubC8209_Loop
2568215SubC8215_Loop
2578222SubC8222_Loop
2588227SubC8227_Loop
259822ASubC822A_Loop
2608231SubC8231
2618257SubC8257
262827DSubC827D
2638283SubC8283
2648285SubC8285_OnCarryClear
26582A1SubC82A1
26682A3SubC82A3_OnCarryClear
26782B7NmiHandler
26882D5SubC82D5_Loop
26982DESubC82DE_Loop
27082E4SubC82E4_Loop
27182EFSubC82EF_Loop
27282FESubC82FE_OnNonzero
2738305SubC8305_OnZero
274832CSubC832C_Loop
2758331IrqHandler
2768332SubC8332_Loop
2778342SubC8342_Loop
278834CSubC834C_Loop
2798357SubC8357_Loop
2808367SubC8367_Loop
281836FSubC836F_Loop
282837BSubC837B_Loop
2838389SubC8389_Loop
284838FSubC838F_Loop
2858392SubC8392
286839ASubC839A_Loop
28783AFSubC83AF_Loop
28883BBSubC83BB
28983D7SubC83D7_Loop
29083DCSubC83DC_Loop
291841ASubC841A_Loop
2928439SubC8439
293844FSubC844F
2948462SubC8462
2958463SubC8463
296846FSubC846F_Loop
2978478SubC8478_Loop
2988484SubC8484_Loop
2998486SubC8486_Loop
3008487SubC8487
301849BSubC849B_OnNonzero
30284B1SubC84B1
30384C8SubC84C8_Loop
30484CFSubC84CF
30584DFSubC84DF_OnCarryClear
30684FBSubC84FB
3078509SubC8509
308851DSubC851D
3098525SubC8525_OnNonnegative
3108542SubC8542_Loop
3118546SubC8546
312854ESubC854E_OnNonzero
3138569SubC8569_OnNonzero
3148588SubC8588_OnNonzero
31585A3SubC85A3_OnNonzero
31685C2SubC85C2_Loop
31785C9SubC85C9
31885E3SubC85E3_Loop
31985F7SubC85F7_Loop
320860ASubC860A_Loop
321860BSubC860B_Loop
322860ESubC860E_Loop
3238611SubC8611
3248614SubC8614
325861CSubC861C
326861FSubC861F
3278627SubC8627
3288634SubC8634
329863BSubC863B
330864ASubC864A_OnNonzero
3318654SubC8654_OnCarryClear
332865ESubC865E_OnNonzero
3338665SubC8665
3348672SubC8672_OnNonzero
3358681SubC8681
336868FSubC868F
3378693SubC8693_OnNonzero
338869DSubC869D
33986C3SubC86C3_Loop
34086C4SubC86C4
34186DDSubC86DD_Loop
34286EASubC86EA
343870BSubC870B_Loop
344870CSubC870C_Loop
3458720SubC8720
3468731SubC8731_Loop
347873DSubC873D_Loop
3488752SubC8752_Loop
3498757SubC8757
3508764SubC8764
3518770SubC8770
3528791SubC8791
3538799SubC8799_OnZero
35487A0SubC87A0
35587ACSubC87AC_Loop
35687BFSubC87BF_Loop
35787C0SubC87C0_Loop
35887CBSubC87CB
35987DASubC87DA_OnCarryClear
36087E5SubC87E5
3618819SubC8819
3628830SubC8830_Loop
3638874SubC8874_Loop
364899ASubC899A
36589A7SubC89A7_OnNonzero
36689BBSubC89BB_Loop
36789BESubC89BE
36889CFSubC89CF_Loop
36989E3SubC89E3_Loop
37089F0SubC89F0
37189F7SubC89F7_Loop
3728A1CSubC8A1C_Loop
3738A30SubC8A30_Loop
3748A33SubC8A33_Loop
3758A3CSubC8A3C_Loop
3768A52SubC8A52_Loop
3778A60SubC8A60_Loop
3788A85SubC8A85_Loop
3798A92SubC8A92_Loop
3808AA2SubC8AA2_Loop
3818AA4SubC8AA4
3828AB2SubC8AB2_Loop
3838AB5SubC8AB5_Loop
3848ABASubC8ABA
3858ABDSubC8ABD
3868AD6SubC8AD6_Loop
3878AE5SubC8AE5_Loop
3888AF5SubC8AF5_Loop
3898B0CSubC8B0C_Loop
3908B15SubC8B15_OnCarrySet
3918B1FSubC8B1F_Loop
3928B30SubC8B30_Loop
3938B33SubC8B33_Loop
3948B43SubC8B43_Loop
3958B4CSubC8B4C_Loop
3968B53SubC8B53_Loop
3978B5ESubC8B5E_Loop
3988B6CSubC8B6C
3998B7ASubC8B7A_Loop
4008B85SubC8B85_Loop
4018B8BSubC8B8B_OnZero
4028B99SubC8B99_Loop
4038BA7SubC8BA7_Loop
4048BB4SubC8BB4_Loop
4058BBESubC8BBE_Loop
4068BD7SubC8BD7_Loop
4078BE0SubC8BE0
4088BECSubC8BEC_Loop
4098C07SubC8C07_Loop
4108C17SubC8C17_Loop
4118C1DSubC8C1D_Loop
4128C2BSubC8C2B_Loop
4138C4BSubC8C4B_Loop
4148C53SubC8C53_Loop
4158C69SubC8C69_Loop
4168C72SubC8C72_OnNonnegative
4178CB1SubC8CB1
4188CC1SubC8CC1_Loop
4198CF4SubC8CF4
4208D03SubC8D03
4218D47SubC8D47_Loop
4228D48SubC8D48
4238D68SubC8D68_Loop
4248D6ASubC8D6A_OnZero
4258D6BSubC8D6B
4268D8BSubC8D8B_Loop
4278DA7SubC8DA7
4288DBBSubC8DBB_Loop
4298DC9SubC8DC9_Loop
4308DCASubC8DCA_Loop
4318DD9SubC8DD9
4328DE7SubC8DE7_Loop
4338E20SubC8E20_OnNonnegative
4348E21SubC8E21
4358E37SubC8E37_Loop
4368E4FSubC8E4F_Loop
4378E73SubC8E73_Loop
4388E76SubC8E76_Loop
4398EB8SubC8EB8_Loop
4408EC3SubC8EC3
4418EDCSubC8EDC_Loop
4428EECSubC8EEC_Loop
4438F0CSubC8F0C
4448F27SubC8F27_Loop
4458F2ASubC8F2A
4468F34SubC8F34_OnCarryClear
4478F3BSubC8F3B
4488F6ASubC8F6A_Loop
4498F7ASubC8F7A_Loop
4508F81SubC8F81_Loop
4518F82SubC8F82_Loop
4528F92SubC8F92_Loop
4538F95SubC8F95_Loop
4548FA2SubC8FA2
4558FC9SubC8FC9
4568FF5SubC8FF5_Loop
4578FF8SubC8FF8
4588FFCSubC8FFC_OnCarryClear
4599008SubC9008
460901BSubC901B
4619028SubC9028
4629048SubC9048_OnCarryClear
4639070SubC9070_Loop
46490ABSubC90AB_OnCarryClear
46590BFSubC90BF_Loop
46690CFSubC90CF_Loop
46790DDSubC90DD_Loop
46890F2SubC90F2
4699100SubC9100
4709124SubC9124
471913CSubC913C_OnCarryClear
4729156SubC9156_OnCarryClear
4739175SubC9175
4749190SubC9190_OnNonnegative
47591A7SubC91A7_OnNegative
47691ACSubC91AC_OnNonnegative
47791B6SubC91B6_OnCarryClear
47891D0SubC91D0_OnNonnegative
47991DASubC91DA_OnNonnegative
48091E4SubC91E4_OnNonnegative
48191EBSubC91EB
4829239SubC9239_Loop
483928FSubC928F_Loop
48492B8SubC92B8_OnNonnegative
48592D9SubC92D9
48692F9SubC92F9
487930BSubC930B
4889329SubC9329_OnZero
489938ESubC938E
4909395SubC9395_Loop
49193A6SubC93A6_Loop
49293A7SubC93A7_Loop
49393BBSubC93BB_Loop
49493CDSubC93CD_OnNonnegative
49593FFSubC93FF_Loop
4969405SubC9405_OnNonnegative
497942CSubC942C
4989436SubC9436_OnCarryClear
4999443SubC9443_Loop
5009455SubC9455_Loop
5019456SubC9456
5029461SubC9461_OnCarryClear
5039490SubC9490
5049496SubC9496_OnCarryClear
50594A7SubC94A7_Loop
50694DDSubC94DD_OnZero
50794F4SubC94F4_Loop
5089508SubC9508
509951ESubC951E_Loop
5109535SubC9535
5119566SubC9566_Loop
512956BSubC956B_OnNonnegative
513956FSubC956F_OnNonnegative
51495A6SubC95A6_Loop
51595D1SubC95D1
51695D5SubC95D5_OnCarryClear
51795FASubC95FA_Loop
51895FFSubC95FF
5199609SubC9609_Loop
5209619SubC9619_Loop
521962ASubC962A_OnCarryClear
5229661SubC9661
5239671SubC9671_OnNonzero
5249680SubC9680_Loop
525968BSubC968B
526968DSubC968D_OnCarryClear
52796AESubC96AE_Loop
52896DCSubC96DC_Loop
52996E0SubC96E0_Loop
53096F8SubC96F8_Loop
53197A7SubC97A7
53297B6SubC97B6_OnCarrySet
53397B9SubC97B9_Loop
53497BASubC97BA_Loop
53597CASubC97CA
53697EASubC97EA_Loop
53797EFSubC97EF
53897F8SubC97F8_Loop
539988FSubC988F
54098B3SubC98B3
54199ECSubC99EC
54299EESubC99EE_OnCarryClear
54399F6SubC99F6_Loop
5449A1DSubC9A1D_Loop
5459A27SubC9A27_Loop
5469A36SubC9A36_Loop
5479A3CSubC9A3C
5489A43SubC9A43_Loop
5499A4DSubC9A4D_Loop
5509A66SubC9A66_Loop
5519A7CSubC9A7C
5529A94SubC9A94_Loop
5539A97SubC9A97_Loop
5549AA2SubC9AA2_Loop
5559AD2SubC9AD2_Loop
5569ADASubC9ADA_Loop
5579AEBSubC9AEB_Loop
5589B05SubC9B05_Loop
5599B0BSubC9B0B
5609B31SubC9B31_Loop
5619B34SubC9B34_Loop
5629B3FSubC9B3F
5639B53SubC9B53_Loop
5649B5FSubC9B5F
5659B68SubC9B68_Loop
5669B84SubC9B84_Loop
5679BA0SubC9BA0_Loop
5689BA6SubC9BA6_Loop
5699BACSubC9BAC_Loop
5709BBBSubC9BBB_Loop
5719BCFSubC9BCF_Loop
5729C2ESubC9C2E
5739C46SubC9C46_Loop
5749C60SubC9C60_Loop
5759C70SubC9C70
5769C95SubC9C95_Loop
5779CA5SubC9CA5
5789CB1SubC9CB1_Loop
5799CBFSubC9CBF
5809CD3SubC9CD3_Loop
5819CDASubC9CDA
5829CDESubC9CDE_OnCarryClear
5839CE7SubC9CE7_OnZero
5849CF2SubC9CF2_Loop
5859E97SubC9E97
5869EA1SubC9EA1_OnNonnegative
5879EA4SubC9EA4_OnNonnegative
5889ED6SubC9ED6_Loop
5899EE3SubC9EE3_Loop
5909EF1SubC9EF1_OnNonnegative
5919F08SubC9F08_Loop
5929F1ASubC9F1A
5939F2ESubC9F2E
5949F3CSubC9F3C
5959F5CSubC9F5C_OnCarrySet
5969F88SubC9F88_OnCarrySet
5979FD5SubC9FD5_Loop
5989FF1SubC9FF1_Loop
5999FF2SubC9FF2_Loop
6009FF5SubC9FF5_OnCarryClear
601A033SubCA033
602A03DSubCA03D_Loop
603A04DSubCA04D_Loop
604A069SubCA069_Loop
605A07ESubCA07E_Loop
606A07FSubCA07F_Loop
607A089SubCA089_OnCarryClear
608A099SubCA099_Loop
609A0C3SubCA0C3_Loop
610A0D2SubCA0D2
611A0FCSubCA0FC_Loop
612A10CSubCA10C_Loop
613A10FSubCA10F_Loop
614A110SubCA110_OnNonzero
615A111SubCA111_OnCarrySet
616A123SubCA123
617A12CSubCA12C_Loop
618A132SubCA132
619A146SubCA146_OnCarryClear
620A14FSubCA14F_Loop
621A156SubCA156
622A16FSubCA16F_Loop
623A1C6SubCA1C6_Loop
624A63DSubCA63D
625A64ASubCA64A_Loop
626A68ASubCA68A
627A6C6SubCA6C6_Loop
628A6CCSubCA6CC_Loop
629A6EFSubCA6EF_Loop
630A6F0SubCA6F0
631A6FFSubCA6FF_Loop
632A717SubCA717_Loop
633A740SubCA740_Loop
634A741SubCA741_Loop
635A74BSubCA74B
636A76ASubCA76A_OnNonnegative
637A796SubCA796
638A7A0SubCA7A0_OnNonnegative
639A7ADSubCA7AD_OnNonnegative
640A7B6SubCA7B6_OnCarrySet
641A7B7SubCA7B7_Loop
642A7B9SubCA7B9_OnNonnegative
643A7C9SubCA7C9
644A7E9SubCA7E9_Loop
645A7F8SubCA7F8_Loop
646A815SubCA815_Loop
647A825SubCA825_Loop
648A855SubCA855_Loop
649A864SubCA864_Loop
650A872SubCA872
651A898SubCA898_OnNonnegative
652A89CSubCA89C_OnNonnegative
653A8D0SubCA8D0_Loop
654A8D1SubCA8D1
655A8FDSubCA8FD_OnNegative
656A90BSubCA90B_Loop
657A90CSubCA90C
658A925SubCA925_Loop
659A926SubCA926_Loop
660A943SubCA943_OnNonnegative
661A975SubCA975
662A99CSubCA99C_Loop
663A99DSubCA99D_Loop
664A9BFSubCA9BF
665A9C4SubCA9C4_Loop
666A9FFSubCA9FF_Loop
667AA02SubCAA02_Loop
668AA35SubCAA35
669AA3BSubCAA3B
670AA48SubCAA48_Loop
671AA4DSubCAA4D
672AA7BSubCAA7B_OnCarryClear
673AA7FSubCAA7F_OnNonnegative
674AAB5SubCAAB5_Loop
675AAB6SubCAAB6
676AAC3SubCAAC3_OnCarryClear
677AACFSubCAACF_Loop
678AAD7SubCAAD7_Loop
679AAD8SubCAAD8_Loop
680AAE5SubCAAE5_Loop
681AB00SubCAB00_Loop
682AB03SubCAB03
683AB29SubCAB29_Loop
684AB39SubCAB39_Loop
685AB3ASubCAB3A_Loop
686AB51SubCAB51_Loop
687AB55SubCAB55_OnNonnegative
688AB7CSubCAB7C
689AB83SubCAB83_OnCarryClear
690ABACSubCABAC_Loop
691ABAESubCABAE
692ABD0SubCABD0_Loop
693ABDCSubCABDC_Loop
694ABE4SubCABE4_Loop
695ABE5SubCABE5
696AC02SubCAC02_Loop
697AC04SubCAC04_OnNonzero
698AC3DSubCAC3D
699AC7FSubCAC7F_Loop
700AC80SubCAC80_Loop
701AC89SubCAC89
702ACB9SubCACB9_OnCarryClear
703ACC6SubCACC6_OnNonnegative
704ACD7SubCACD7_OnCarryClear
705ACE8SubCACE8_OnCarryClear
706ACFFSubCACFF_OnCarryClear
707AD1ASubCAD1A_OnCarryClear
708AD28SubCAD28
709AD34SubCAD34_OnCarryClear
710AD47SubCAD47
711AD49SubCAD49_OnNonnegative
712AD52SubCAD52
713AD61SubCAD61_OnCarryClear
714AD76SubCAD76_OnCarryClear
715AD8BSubCAD8B_OnCarryClear
716ADE6SubCADE6
717AE15SubCAE15
718AE17SubCAE17_OnCarryClear
719AE28SubCAE28
720AE2ASubCAE2A_OnCarryClear
721AE3DSubCAE3D
722AE4BSubCAE4B
723AE5ASubCAE5A_OnCarryClear
724AE6BSubCAE6B_Loop
725AE7BSubCAE7B
726AE8DSubCAE8D_OnNonzero
727AE9ESubCAE9E
728AEACSubCAEAC_Loop
729AECBSubCAECB_Loop
730AEE5SubCAEE5
731AEF4SubCAEF4_Loop
732AEF7SubCAEF7
733AEFFSubCAEFF
734AF01SubCAF01_OnNonnegative
735AF0FSubCAF0F
736AF1BSubCAF1B_OnNonzero
737AF1CSubCAF1C_Loop
738AF29SubCAF29_Loop
739B0D7SubCB0D7
740B0DFSubCB0DF_OnCarryClear
741B0EBSubCB0EB
742B10FSubCB10F
743B146SubCB146_OnCarryClear
744B153SubCB153_OnCarryClear
745B16ASubCB16A_OnCarryClear
746B190SubCB190_OnNonnegative
747B1A2SubCB1A2_OnCarryClear
748B1C0SubCB1C0_OnCarryClear
749B1DESubCB1DE_OnCarryClear
750B1F1SubCB1F1_Loop
751B1F8SubCB1F8_OnCarryClear
752B214SubCB214
753B22ASubCB22A_Loop
754B236SubCB236_Loop
755B23CSubCB23C_Loop
756B24BSubCB24B_Loop
757B24DSubCB24D_OnNonnegative
758B257SubCB257_Loop
759B271SubCB271
760B279SubCB279_OnNonnegative
761B289SubCB289_Loop
762B295SubCB295_OnCarryClear
763B2B1SubCB2B1_Loop
764B2C0SubCB2C0_OnNonzero
765B2DASubCB2DA
766B3D6SubCB3D6
767B405SubCB405_OnCarryClear
768B414SubCB414_Loop
769B415SubCB415
770B41ASubCB41A_OnNonnegative
771B42ASubCB42A_Loop
772B436SubCB436_OnCarryClear
773B45DSubCB45D_OnNonzero
774B467SubCB467_Loop
775B469SubCB469_Loop
776B480SubCB480_OnNegative
777B486SubCB486_OnNonnegative
778B497SubCB497_OnCarryClear
779B4A5SubCB4A5_OnZero
780B4B5SubCB4B5_Loop
781B4C0SubCB4C0_OnNonzero
782B4C4SubCB4C4_Loop
783B4DFSubCB4DF
784B4F2SubCB4F2_Loop
785B4F7SubCB4F7_OnNonnegative
786B507SubCB507_Loop
787B513SubCB513_OnCarryClear
788B53DSubCB53D_OnNonzero
789B557SubCB557_OnZero
790B563SubCB563_Loop
791B567SubCB567_Loop
792B57DSubCB57D_OnNonzero
793B640SubCB640
794B759SubCB759
795B770SubCB770_OnCarryClear
796B77BSubCB77B_Loop
797B792SubCB792_Loop
798B8AESubCB8AE
799B8B3SubCB8B3_OnNonnegative
800C819SubCC819
801C844SubCC844
802C86FSubCC86F
803C89ASubCC89A
804C8BBSubCC8BB
805C8D2SubCC8D2
806C900SubCC900
807C90DSubCC90D
808C927SubCC927
809C93ESubCC93E
810C94BSubCC94B
811C96BSubCC96B
812C978SubCC978
813C985SubCC985
814C9D3SubCC9D3
815C9E0SubCC9E0
816C9EDSubCC9ED
817C9FASubCC9FA
818CF09SubCCF09
819CF21SubCCF21
820CF37SubCCF37
821CF40SubCCF40_Loop
822CF4ESubCCF4E
823CF61SubCCF61_Loop
824CF62SubCCF62_Loop
825CF69SubCCF69_Loop
826CFA2SubCCFA2
827CFBCSubCCFBC
828CFCCSubCCFCC_Loop
829CFD0SubCCFD0
830CFF7SubCCFF7_OnNonnegative
831CFFESubCCFFE_OnZero
832D01FSubCD01F_Loop
833D020SubCD020_Loop
834D021SubCD021_OnCarrySet
835D027SubCD027_Loop
836D04CSubCD04C
837D05BSubCD05B
838D06ASubCD06A_Loop
839D06BSubCD06B_Loop
840D080SubCD080
841D085SubCD085
842D08DSubCD08D_Loop
843D097SubCD097_Loop
844D09ASubCD09A_Loop
845D09CSubCD09C_Loop
846D09DSubCD09D
847D0AFSubCD0AF
848D0BBSubCD0BB_Loop
849D0BCSubCD0BC_Loop
850D0C7SubCD0C7
851D0D0SubCD0D0
852D0D2SubCD0D2_OnNonzero
853D0DASubCD0DA_Loop
854D0E1SubCD0E1_Loop
855D0EDSubCD0ED_Loop
856D0F7SubCD0F7
857D0FFSubCD0FF_Loop
858D10ASubCD10A_Loop
859D10FSubCD10F
860D114SubCD114_Loop
861D12BSubCD12B_Loop
862D135SubCD135_OnCarryClear
863D157SubCD157_Loop
864D16ESubCD16E_Loop
865D17ESubCD17E_Loop
866D188SubCD188_OnNonzero
867D18BSubCD18B_Loop
868D193SubCD193_OnNonnegative
869D194SubCD194_Loop
870D19FSubCD19F
871D1A1SubCD1A1_OnCarryClear
872D1ABSubCD1AB_Loop
873D1C3SubCD1C3_Loop
874D1CFSubCD1CF_Loop
875D1E6SubCD1E6_Loop
876D1F2SubCD1F2_Loop
877D1FESubCD1FE_Loop
878D206SubCD206_Loop
879D223SubCD223_OnCarryClear
880D240SubCD240_Loop
881D25BSubCD25B_Loop
882D275SubCD275_Loop
883D28ESubCD28E_Loop
884D297SubCD297
885D298SubCD298
886D2B4SubCD2B4_Loop
887D2C4SubCD2C4_Loop
888D2CBSubCD2CB_Loop
889D2CESubCD2CE
890D2DESubCD2DE_Loop
891D2DFSubCD2DF
892D2EDSubCD2ED
893D2EFSubCD2EF_OnCarryClear
894D300SubCD300_Loop
895D328SubCD328_Loop
896D348SubCD348_Loop
897D34FSubCD34F_Loop
898D359SubCD359
899D35BSubCD35B_OnCarryClear
900D368SubCD368_Loop
901D37ASubCD37A_Loop
902D390SubCD390_Loop
903D397SubCD397_Loop
904D3A1SubCD3A1
905D3ADSubCD3AD_Loop
906D3BDSubCD3BD_Loop
907D3C4SubCD3C4_Loop
908D3C5SubCD3C5
909D3E1SubCD3E1_OnCarryClear
910D3F2SubCD3F2_Loop
911D41ASubCD41A_Loop
912D434SubCD434_Loop
913D442SubCD442_Loop
914D44CSubCD44C
915D478SubCD478_Loop
916D485SubCD485
917D488SubCD488_Loop
918D4A5SubCD4A5
919D4BCSubCD4BC_OnCarryClear
920D4BDSubCD4BD_Loop
921D4CCSubCD4CC_Loop
922D4D1SubCD4D1_Loop
923D4F5SubCD4F5_Loop
924D50DSubCD50D_Loop
925D510SubCD510_Loop
926D515SubCD515_Loop
927D524SubCD524_Loop
928D529SubCD529_Loop
929D540SubCD540_Loop
930D54FSubCD54F_Loop
931D564SubCD564_Loop
932D570SubCD570_Loop
933D5A9SubCD5A9_Loop
934D5ABSubCD5AB_OnNonnegative
935D5B0SubCD5B0_OnNonnegative
936D5BCSubCD5BC_Loop
937D611SubCD611_Loop
938D625SubCD625
939D63BSubCD63B_Loop
940D642SubCD642_Loop
941D64DSubCD64D_Loop
942D69BSubCD69B_Loop
943D6B3SubCD6B3_Loop
944D6CASubCD6CA_Loop
945D6D3SubCD6D3_OnNonnegative
946D71ASubCD71A
947D71CSubCD71C_OnCarryClear
948D739SubCD739_Loop
949D866SubCD866
950D86CSubCD86C_OnCarryClear
951D884SubCD884_Loop
952D89ESubCD89E_Loop
953D8A7SubCD8A7_Loop
954D8A8SubCD8A8_Loop
955D8C2SubCD8C2_OnNonzero
956D90BSubCD90B
957D946SubCD946_Loop
958D953SubCD953_Loop
959D967SubCD967_Loop
960D968SubCD968
961D980SubCD980_Loop
962D993SubCD993_Loop
963D9A7SubCD9A7_Loop
964D9D2SubCD9D2_Loop
965D9F1SubCD9F1
966DA02SubCDA02_Loop
967DA0ESubCDA0E_OnNonzero
968DA0FSubCDA0F
969DA37SubCDA37_Loop
970DA44SubCDA44
971DA5ASubCDA5A_Loop
972DA67SubCDA67
973DA81SubCDA81_Loop
974DA91SubCDA91_Loop
975DAA3SubCDAA3_Loop
976DAB7SubCDAB7
977DAB8SubCDAB8
978DACESubCDACE_Loop
979DACFSubCDACF_Loop
980DAD8SubCDAD8
981DB16SubCDB16_Loop
982DB17SubCDB17
983DB30SubCDB30_Loop
984DB3FSubCDB3F_Loop
985DB4DSubCDB4D_Loop
986DB58SubCDB58_Loop
987DB6CSubCDB6C_Loop
988DB8ASubCDB8A
989DBA1SubCDBA1_Loop
990DBAESubCDBAE_Loop
991DBBBSubCDBBB_Loop
992DBBCSubCDBBC