Files
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

1107 lines
19 KiB
Plaintext

C000 Reset
C057 SubCC057
C05A NmiHandler
C0B8 SubCC0B8
C0C3 SubCC0C3
C0C5 SubCC0C5
C0CB SubCC0CB
C0D0 SubCC0D0
C0E4 SubCC0E4
C0F9 SubCC0F9
C108 SubCC108
C1B7 SubCC1B7
C1D5 SubCC1D5
C1EA SubCC1EA
C250 SubCC250
C252 SubCC252
C25D SubCC25D
C2A5 SubCC2A5
C2A7 SubCC2A7
C2AB SubCC2AB
C303 SubCC303
C342 SubCC342
C3AA SubCC3AA
C3B8 SubCC3B8
C3BE SubCC3BE
C3C1 SubCC3C1
C3D6 SubCC3D6
C3E0 SubCC3E0
C3F5 SubCC3F5
C402 SubCC402
C444 SubCC444
C458 SubCC458
C45D SubCC45D
C4AA SubCC4AA
C4BA SubCC4BA
C4C8 SubCC4C8
C4CD SubCC4CD
C4E3 SubCC4E3
C505 SubCC505
C53F SubCC53F
C556 SubCC556
C564 SubCC564
C58F SubCC58F
C5B2 SubCC5B2
C5C3 SubCC5C3
C5CB SubCC5CB
C5F7 SubCC5F7
C606 SubCC606
C61D SubCC61D
C62D SubCC62D
C637 SubCC637
C63A SubCC63A
C643 SubCC643
C64B SubCC64B
C662 SubCC662
C67B SubCC67B
C6AD SubCC6AD
C6C4 SubCC6C4
C6F3 SubCC6F3
C6F7 SubCC6F7
C753 SubCC753
C81A SubCC81A
C822 SubCC822
C835 SubCC835
C889 SubCC889
C8FC SubCC8FC
C906 SubCC906
C991 SubCC991
C9CE SubCC9CE
C9DD SubCC9DD
C9EC SubCC9EC
C9F2 SubCC9F2
CA04 SubCCA04
CA11 SubCCA11
CA25 SubCCA25
CA31 SubCCA31
CA3B SubCCA3B
CA4B SubCCA4B
CA4F SubCCA4F
CA55 SubCCA55
CA5C SubCCA5C
CAB1 SubCCAB1
CB2D SubCCB2D
CB51 SubCCB51
CB55 SubCCB55
CBDA SubCCBDA
CBE4 SubCCBE4
CC16 SubCCC16
CC20 SubCCC20
CC50 SubCCC50
CC5B SubCCC5B
CC62 SubCCC62
CC7E SubCCC7E
CC87 SubCCC87
CC8F SubCCC8F
CC94 SubCCC94
CCB6 SubCCCB6
CCD0 SubCCCD0
CCD3 SubCCCD3
CCD9 SubCCCD9
CD28 SubCCD28
CD2D SubCCD2D
CD32 SubCCD32
CD61 SubCCD61
CD68 SubCCD68
CDC7 SubCCDC7
CDE8 SubCCDE8
CE6D SubCCE6D
CE8E SubCCE8E
CE9E SubCCE9E
CEAB SubCCEAB
CEB7 SubCCEB7
CEE3 SubCCEE3
CEE5 SubCCEE5
CEF2 SubCCEF2
CF0D SubCCF0D
CF49 SubCCF49
CF58 SubCCF58
CF9D SubCCF9D
CFB3 SubCCFB3
CFCE SubCCFCE
CFDE SubCCFDE
D001 SubCD001
D009 SubCD009
D0AD SubCD0AD
D0DA SubCD0DA
D10C SubCD10C
D124 SubCD124
D142 SubCD142
D1C4 SubCD1C4
D1E4 SubCD1E4
D1E8 SubCD1E8
D280 SubCD280
D282 SubCD282
D2FD SubCD2FD
D31E SubCD31E
D342 SubCD342
D389 SubCD389
D3F3 SubCD3F3
D48E SubCD48E
D4CE SubCD4CE
D4E4 SubCD4E4
D544 SubCD544
D54E SubCD54E
D575 SubCD575
D597 SubCD597
D5DF SubCD5DF
D621 SubCD621
D657 SubCD657
D665 SubCD665
D714 SubCD714
D76D SubCD76D
D807 SubCD807
D814 SubCD814
D8E4 SubCD8E4
D9AB SubCD9AB
D9F3 SubCD9F3
D9F7 SubCD9F7
D9FB SubCD9FB
DA05 SubCDA05
DA11 SubCDA11
DADA SubCDADA
DAFD SubCDAFD
DB01 SubCDB01
DB31 SubCDB31
DB87 SubCDB87
DB97 SubCDB97
DBB6 SubCDBB6
DBD1 SubCDBD1
DC58 SubCDC58
DC95 SubCDC95
DCAB SubCDCAB
DCDC SubCDCDC
E484 SubCE484
E4E0 SubCE4E0
E509 SubCE509
E521 SubCE521
E52D SubCE52D
E562 SubCE562
E59A SubCE59A
E5B0 SubCE5B0
E61D SubCE61D
E6B0 SubCE6B0
E6C9 SubCE6C9
E79F SubCE79F
E7BA SubCE7BA
E7EB SubCE7EB
E82C SubCE82C
E838 SubCE838
E842 SubCE842
E845 SubCE845
E903 SubCE903
E91F SubCE91F
E92E SubCE92E
E95C SubCE95C
E969 SubCE969
E97E SubCE97E
E9BC SubCE9BC
EAC4 SubCEAC4
EB98 SubCEB98
EC94 SubCEC94
EC9C SubCEC9C
ED21 SubCED21
ED26 SubCED26
ED42 SubCED42
ED51 SubCED51
ED66 SubCED66
EDB3 SubCEDB3
EDC0 SubCEDC0
EDE7 SubCEDE7
EDF3 SubCEDF3
EDFE SubCEDFE
EE0A SubCEE0A
EE28 SubCEE28
EEC2 SubCEEC2
EED0 SubCEED0
EED9 SubCEED9
EF53 SubCEF53
EF74 SubCEF74
F06E SubCF06E
F078 SubCF078
F188 SubCF188
F1CF SubCF1CF
F23F SubCF23F
F2DB SubCF2DB
F342 SubCF342
F36D SubCF36D
F39A SubCF39A
F3B0 SubCF3B0
F3C3 SubCF3C3
F3D4 SubCF3D4
F408 SubCF408
F42E SubCF42E
F432 SubCF432
F479 SubCF479
F51D SubCF51D
F540 SubCF540
F571 SubCF571
F5C6 SubCF5C6
F601 SubCF601
F612 SubCF612
F649 SubCF649
F666 SubCF666
F6CD SubCF6CD
F758 SubCF758
F7DA SubCF7DA
F7DF SubCF7DF
F7E4 SubCF7E4
F7E9 SubCF7E9
F7EE SubCF7EE
F7FC SubCF7FC
F80D SubCF80D
F87C SubCF87C
F8C8 SubCF8C8
F8E1 SubCF8E1
F975 SubCF975
F9C9 SubCF9C9
FA73 SubCFA73
FAA9 SubCFAA9
# ---- derived internal branch-target names ----
C000 Reset
C002 SubCC002_OnNonnegative
C007 SubCC007_OnNonnegative
C014 SubCC014_OnNonzero
C01F SubCC01F_Loop
C023 SubCC023_OnNonzero
C02D SubCC02D_Loop
C037 SubCC037_OnNonzero
C046 SubCC046_Loop
C04D SubCC04D_OnNonzero
C057 SubCC057
C05A NmiHandler
C082 SubCC082_Loop
C084 SubCC084_Loop
C089 SubCC089_Loop
C0A5 SubCC0A5_Loop
C0B2 SubCC0B2_Loop
C0B8 SubCC0B8
C0C3 SubCC0C3
C0C5 SubCC0C5
C0CB SubCC0CB
C0D0 SubCC0D0
C0E4 SubCC0E4
C0F9 SubCC0F9
C107 SubCC107_Loop
C108 SubCC108
C117 SubCC117_Loop
C12B SubCC12B_Loop
C138 SubCC138_Loop
C14E SubCC14E_OnNonzero
C160 SubCC160_Loop
C168 SubCC168_Loop
C179 SubCC179_Loop
C181 SubCC181_Loop
C1A5 SubCC1A5_OnCarryClear
C1A6 SubCC1A6_Loop
C1B7 SubCC1B7
C1C8 SubCC1C8_Loop
C1CB SubCC1CB_OnNonzero
C1D5 SubCC1D5
C1EA SubCC1EA
C1F9 SubCC1F9_Loop
C20C SubCC20C_OnZero
C250 SubCC250
C252 SubCC252
C254 SubCC254_OnNonzero
C257 SubCC257_OnZero
C25D SubCC25D
C26E SubCC26E_Loop
C271 SubCC271_Loop
C28F SubCC28F_Loop
C2A5 SubCC2A5
C2A7 SubCC2A7
C2AB SubCC2AB
C2B1 SubCC2B1_OnNonzero
C2B2 SubCC2B2_Loop
C2D2 SubCC2D2_Loop
C2EB SubCC2EB_Loop
C303 SubCC303
C31B SubCC31B_Loop
C326 SubCC326_OnNonzero
C32D SubCC32D_OnNonzero
C340 SubCC340_Loop
C342 SubCC342
C34B SubCC34B_Loop
C399 SubCC399_Loop
C39A SubCC39A_Loop
C3AA SubCC3AA
C3B8 SubCC3B8
C3BE SubCC3BE
C3C1 SubCC3C1
C3D6 SubCC3D6
C3E0 SubCC3E0
C3E2 SubCC3E2_Loop
C3EC SubCC3EC_OnNonzero
C3F5 SubCC3F5
C3FA SubCC3FA_OnNonzero
C402 SubCC402
C40D SubCC40D_OnNonzero
C444 SubCC444
C44E SubCC44E_Loop
C452 SubCC452_Loop
C454 SubCC454_Loop
C458 SubCC458
C45D SubCC45D
C480 SubCC480_Loop
C488 SubCC488_Loop
C489 SubCC489_Loop
C4AA SubCC4AA
C4AF SubCC4AF_OnNonzero
C4BA SubCC4BA
C4C8 SubCC4C8
C4CD SubCC4CD
C4E3 SubCC4E3
C4EA SubCC4EA_Loop
C505 SubCC505
C509 SubCC509_OnZero
C516 SubCC516_OnZero
C527 SubCC527_Loop
C52F SubCC52F_Loop
C530 SubCC530_Loop
C537 SubCC537_OnNonzero
C53F SubCC53F
C548 SubCC548_Loop
C556 SubCC556
C55A SubCC55A_OnNonzero
C564 SubCC564
C56F SubCC56F_Loop
C571 SubCC571_OnNonzero
C578 SubCC578_OnNonzero
C584 SubCC584_Loop
C586 SubCC586_OnNonzero
C58F SubCC58F
C591 SubCC591_OnNonnegative
C5B2 SubCC5B2
C5B6 SubCC5B6_OnNonnegative
C5C3 SubCC5C3
C5CB SubCC5CB
C5E0 SubCC5E0_Loop
C5EC SubCC5EC_Loop
C5F7 SubCC5F7
C606 SubCC606
C613 SubCC613_Loop
C61D SubCC61D
C622 SubCC622_OnNonzero
C62D SubCC62D
C637 SubCC637
C63A SubCC63A
C643 SubCC643
C64A SubCC64A_OnCarrySet
C64B SubCC64B
C662 SubCC662
C670 SubCC670_Loop
C677 SubCC677_Loop
C67B SubCC67B
C68D SubCC68D_OnNonnegative
C693 SubCC693_Loop
C6A8 SubCC6A8_Loop
C6AD SubCC6AD
C6C3 SubCC6C3_Loop
C6C4 SubCC6C4
C6D3 SubCC6D3_Loop
C6DC SubCC6DC_OnNonzero
C6ED SubCC6ED_OnNonnegative
C6F2 SubCC6F2_Loop
C6F3 SubCC6F3
C6F7 SubCC6F7
C70D SubCC70D_Loop
C71D SubCC71D_Loop
C720 SubCC720_Loop
C721 SubCC721_Loop
C731 SubCC731_Loop
C73A SubCC73A_Loop
C73C SubCC73C_OnNonnegative
C748 SubCC748_Loop
C74A SubCC74A_OnNonnegative
C752 SubCC752_Loop
C753 SubCC753
C81A SubCC81A
C822 SubCC822
C830 SubCC830_Loop
C835 SubCC835
C845 SubCC845_Loop
C85F SubCC85F_OnNonzero
C861 SubCC861_OnNonzero
C87C SubCC87C_OnNonzero
C889 SubCC889
C897 SubCC897_Loop
C8B3 SubCC8B3_Loop
C8B5 SubCC8B5_Loop
C8C1 SubCC8C1_Loop
C8D3 SubCC8D3_Loop
C8D7 SubCC8D7_Loop
C8D9 SubCC8D9_Loop
C8E2 SubCC8E2_Loop
C8FC SubCC8FC
C900 SubCC900_OnNonnegative
C906 SubCC906
C925 SubCC925_Loop
C991 SubCC991
C9A0 SubCC9A0_Loop
C9BD SubCC9BD_Loop
C9C6 SubCC9C6_Loop
C9CE SubCC9CE
C9DD SubCC9DD
C9EC SubCC9EC
C9F2 SubCC9F2
CA04 SubCCA04
CA11 SubCCA11
CA25 SubCCA25
CA29 SubCCA29_OnZero
CA2F SubCCA2F_OnNonzero
CA31 SubCCA31
CA3B SubCCA3B
CA3D SubCCA3D_OnNonnegative
CA4B SubCCA4B
CA4F SubCCA4F
CA55 SubCCA55
CA5C SubCCA5C
CA63 SubCCA63_OnNonzero
CA80 SubCCA80_OnNonzero
CA8D SubCCA8D_Loop
CA8F SubCCA8F_OnNonzero
CAB0 SubCCAB0_Loop
CAB1 SubCCAB1
CAC1 SubCCAC1_Loop
CAC3 SubCCAC3_Loop
CAD3 SubCCAD3_OnNonzero
CAD5 SubCCAD5_OnNonzero
CAE3 SubCCAE3_OnNonzero
CB08 SubCCB08_OnNonzero
CB0A SubCCB0A_Loop
CB1C SubCCB1C_Loop
CB24 SubCCB24_Loop
CB2D SubCCB2D
CB40 SubCCB40_OnNonzero
CB4B SubCCB4B_Loop
CB51 SubCCB51
CB55 SubCCB55
CB57 SubCCB57_Loop
CB75 SubCCB75_Loop
CB78 SubCCB78_Loop
CB7B SubCCB7B_Loop
CB85 SubCCB85_Loop
CB88 SubCCB88_Loop
CBDA SubCCBDA
CBE4 SubCCBE4
CC16 SubCCC16
CC20 SubCCC20
CC3B SubCCC3B_Loop
CC40 SubCCC40_Loop
CC4B SubCCC4B_Loop
CC50 SubCCC50
CC5B SubCCC5B
CC62 SubCCC62
CC7E SubCCC7E
CC87 SubCCC87
CC8C SubCCC8C_Loop
CC8F SubCCC8F
CC94 SubCCC94
CCB2 SubCCCB2_Loop
CCB4 SubCCCB4_Loop
CCB6 SubCCCB6
CCD0 SubCCCD0
CCD3 SubCCCD3
CCD9 SubCCCD9
CD28 SubCCD28
CD2D SubCCD2D
CD32 SubCCD32
CD4D SubCCD4D_Loop
CD51 SubCCD51_Loop
CD53 SubCCD53_Loop
CD61 SubCCD61
CD67 SubCCD67_OnNonzero
CD68 SubCCD68
CD80 SubCCD80_Loop
CD8F SubCCD8F_Loop
CD97 SubCCD97_OnCarryClear
CDA0 SubCCDA0_Loop
CDB3 SubCCDB3_Loop
CDB7 SubCCDB7_Loop
CDC2 SubCCDC2_Loop
CDC4 SubCCDC4_Loop
CDC7 SubCCDC7
CDDD SubCCDDD_Loop
CDE7 SubCCDE7_OnCarryClear
CDE8 SubCCDE8
CE0E SubCCE0E_Loop
CE26 SubCCE26_Loop
CE30 SubCCE30_Loop
CE43 SubCCE43_Loop
CE54 SubCCE54_Loop
CE6D SubCCE6D
CE84 SubCCE84_Loop
CE8D SubCCE8D_Loop
CE8E SubCCE8E
CE9E SubCCE9E
CEAB SubCCEAB
CEB7 SubCCEB7
CEE3 SubCCEE3
CEE5 SubCCEE5
CEF2 SubCCEF2
CEFA SubCCEFA_Loop
CF03 SubCCF03_Loop
CF0D SubCCF0D
CF30 SubCCF30_OnNonzero
CF3B SubCCF3B_Loop
CF49 SubCCF49
CF55 SubCCF55_Loop
CF58 SubCCF58
CF86 SubCCF86_Loop
CF88 SubCCF88_Loop
CF9D SubCCF9D
CF9F SubCCF9F_OnZero
CFB3 SubCCFB3
CFCE SubCCFCE
CFD0 SubCCFD0_OnNonnegative
CFDE SubCCFDE
CFE4 SubCCFE4_OnNonzero
CFE9 SubCCFE9_OnNonzero
D000 SubCD000_OnZero
D001 SubCD001
D009 SubCD009
D05F SubCD05F_Loop
D078 SubCD078_Loop
D090 SubCD090_Loop
D096 SubCD096_Loop
D099 SubCD099_Loop
D0AC SubCD0AC_Loop
D0AD SubCD0AD
D0B3 SubCD0B3_OnNonzero
D0CD SubCD0CD_Loop
D0D7 SubCD0D7_Loop
D0DA SubCD0DA
D0E5 SubCD0E5_Loop
D0EA SubCD0EA_Loop
D102 SubCD102_Loop
D10C SubCD10C
D115 SubCD115_Loop
D117 SubCD117_Loop
D120 SubCD120_Loop
D124 SubCD124
D128 SubCD128_OnNonzero
D139 SubCD139_Loop
D141 SubCD141_Loop
D142 SubCD142
D153 SubCD153_Loop
D1C4 SubCD1C4
D1DC SubCD1DC_OnZero
D1E4 SubCD1E4
D1E8 SubCD1E8
D206 SubCD206_OnNonzero
D21D SubCD21D_Loop
D243 SubCD243_Loop
D255 SubCD255_Loop
D270 SubCD270_OnNonzero
D280 SubCD280
D282 SubCD282
D291 SubCD291_Loop
D295 SubCD295_Loop
D2B6 SubCD2B6_OnNonzero
D2C2 SubCD2C2_OnNonzero
D2C9 SubCD2C9_Loop
D2CD SubCD2CD_Loop
D2FD SubCD2FD
D31E SubCD31E
D342 SubCD342
D35F SubCD35F_OnNonzero
D365 SubCD365_Loop
D375 SubCD375_Loop
D388 SubCD388_OnZero
D389 SubCD389
D38B SubCD38B_OnNonzero
D398 SubCD398_OnZero
D39B SubCD39B_Loop
D3A2 SubCD3A2_OnNonzero
D3F3 SubCD3F3
D40A SubCD40A_Loop
D41F SubCD41F_Loop
D426 SubCD426_OnNonnegative
D42B SubCD42B_Loop
D436 SubCD436_Loop
D439 SubCD439_Loop
D449 SubCD449_OnNonnegative
D453 SubCD453_Loop
D45D SubCD45D_Loop
D464 SubCD464_OnNonnegative
D46E SubCD46E_Loop
D47D SubCD47D_Loop
D481 SubCD481_Loop
D486 SubCD486_Loop
D48D SubCD48D_Loop
D48E SubCD48E
D48F SubCD48F_Loop
D490 SubCD490_Loop
D491 SubCD491_Loop
D4BB SubCD4BB_Loop
D4C4 SubCD4C4_Loop
D4CE SubCD4CE
D4DF SubCD4DF_Loop
D4E4 SubCD4E4
D4F3 SubCD4F3_Loop
D4F4 SubCD4F4_Loop
D505 SubCD505_Loop
D50D SubCD50D_Loop
D525 SubCD525_Loop
D53C SubCD53C_OnNonzero
D544 SubCD544
D54E SubCD54E
D550 SubCD550_OnNonzero
D55F SubCD55F_Loop
D575 SubCD575
D58C SubCD58C_OnNonnegative
D597 SubCD597
D5AA SubCD5AA_Loop
D5C7 SubCD5C7_OnNonzero
D5D4 SubCD5D4_OnNonzero
D5DF SubCD5DF
D5F1 SubCD5F1_Loop
D5F2 SubCD5F2_Loop
D5FC SubCD5FC_Loop
D5FE SubCD5FE_Loop
D616 SubCD616_OnNonzero
D621 SubCD621
D624 SubCD624_Loop
D627 SubCD627_Loop
D62B SubCD62B_OnNonzero
D657 SubCD657
D665 SubCD665
D714 SubCD714
D76D SubCD76D
D777 SubCD777_Loop
D78F SubCD78F_Loop
D7A0 SubCD7A0_Loop
D7B4 SubCD7B4_Loop
D7C1 SubCD7C1_Loop
D807 SubCD807
D814 SubCD814
D820 SubCD820_Loop
D82E SubCD82E_Loop
D839 SubCD839_OnNegative
D83F SubCD83F_Loop
D84A SubCD84A_Loop
D858 SubCD858_Loop
D860 SubCD860_Loop
D86A SubCD86A_Loop
D86F SubCD86F_Loop
D87F SubCD87F_Loop
D885 SubCD885_Loop
D889 SubCD889_Loop
D8DD SubCD8DD_OnCarrySet
D8E4 SubCD8E4
D8F2 SubCD8F2_Loop
D8FF SubCD8FF_Loop
D908 SubCD908_Loop
D912 SubCD912_Loop
D91A SubCD91A_Loop
D920 SubCD920_Loop
D924 SubCD924_Loop
D935 SubCD935_Loop
D93D SubCD93D_Loop
D943 SubCD943_Loop
D945 SubCD945_Loop
D94E SubCD94E_Loop
D9AB SubCD9AB
D9B8 SubCD9B8_Loop
D9F3 SubCD9F3
D9F7 SubCD9F7
D9FB SubCD9FB
D9FD SubCD9FD_Loop
DA05 SubCDA05
DA0F SubCDA0F_Loop
DA10 SubCDA10_Loop
DA11 SubCDA11
DA19 SubCDA19_Loop
DA20 SubCDA20_Loop
DA2D SubCDA2D_Loop
DA3E SubCDA3E_Loop
DA60 SubCDA60_Loop
DA71 SubCDA71_Loop
DA76 SubCDA76_Loop
DA9C SubCDA9C_Loop
DAAE SubCDAAE_Loop
DAB3 SubCDAB3_Loop
DAD2 SubCDAD2_Loop
DADA SubCDADA
DADF SubCDADF_Loop
DAE4 SubCDAE4_Loop
DAF7 SubCDAF7_Loop
DAFD SubCDAFD
DAFF SubCDAFF_Loop
DB01 SubCDB01
DB13 SubCDB13_Loop
DB31 SubCDB31
DB36 SubCDB36_Loop
DB56 SubCDB56_Loop
DB5B SubCDB5B_Loop
DB74 SubCDB74_Loop
DB7E SubCDB7E_Loop
DB80 SubCDB80_Loop
DB82 SubCDB82_Loop
DB87 SubCDB87
DB97 SubCDB97
DBB6 SubCDBB6
DBCE SubCDBCE_Loop
DBD1 SubCDBD1
DBDA SubCDBDA_Loop
DBE7 SubCDBE7_Loop
DBF6 SubCDBF6_Loop
DBF7 SubCDBF7_OnNonzero
DC17 SubCDC17_Loop
DC1B SubCDC1B_OnZero
DC21 SubCDC21_Loop
DC27 SubCDC27_Loop
DC2C SubCDC2C_Loop
DC2D SubCDC2D_Loop
DC38 SubCDC38_Loop
DC58 SubCDC58
DC65 SubCDC65_Loop
DC68 SubCDC68_Loop
DC6C SubCDC6C_Loop
DC8A SubCDC8A_Loop
DC95 SubCDC95
DC9B SubCDC9B_Loop
DCAB SubCDCAB
DCB3 SubCDCB3_Loop
DCC0 SubCDCC0_Loop
DCC1 SubCDCC1_Loop
DCC6 SubCDCC6_Loop
DCD4 SubCDCD4_Loop
DCDC SubCDCDC
DCDF SubCDCDF_Loop
DCE6 SubCDCE6_Loop
E484 SubCE484
E497 SubCE497_Loop
E4AA SubCE4AA_OnNonzero
E4B3 SubCE4B3_OnNonzero
E4B4 SubCE4B4_Loop
E4D1 SubCE4D1_OnNonnegative
E4E0 SubCE4E0
E504 SubCE504_Loop
E509 SubCE509
E521 SubCE521
E52D SubCE52D
E562 SubCE562
E578 SubCE578_Loop
E581 SubCE581_Loop
E589 SubCE589_OnNonnegative
E593 SubCE593_Loop
E594 SubCE594_Loop
E59A SubCE59A
E5AC SubCE5AC_Loop
E5AE SubCE5AE_Loop
E5B0 SubCE5B0
E5D1 SubCE5D1_Loop
E601 SubCE601_Loop
E618 SubCE618_Loop
E61C SubCE61C_Loop
E61D SubCE61D
E62D SubCE62D_Loop
E631 SubCE631_OnCarrySet
E632 SubCE632_Loop
E636 SubCE636_Loop
E64C SubCE64C_Loop
E659 SubCE659_Loop
E661 SubCE661_Loop
E667 SubCE667_OnCarryClear
E685 SubCE685_Loop
E693 SubCE693_Loop
E69F SubCE69F_Loop
E6B0 SubCE6B0
E6C9 SubCE6C9
E6D8 SubCE6D8_Loop
E79F SubCE79F
E7A9 SubCE7A9_OnNonzero
E7B3 SubCE7B3_Loop
E7B9 SubCE7B9_Loop
E7BA SubCE7BA
E7D2 SubCE7D2_OnNonnegative
E7EB SubCE7EB
E7FE SubCE7FE_Loop
E80A SubCE80A_Loop
E814 SubCE814_Loop
E81A SubCE81A_Loop
E823 SubCE823_Loop
E82B SubCE82B_Loop
E82C SubCE82C
E837 SubCE837_Loop
E838 SubCE838
E842 SubCE842
E845 SubCE845
E849 SubCE849_OnNonzero
E86A SubCE86A_Loop
E86C SubCE86C_Loop
E88A SubCE88A_Loop
E88F SubCE88F_Loop
E897 SubCE897_Loop
E89D SubCE89D_OnNonnegative
E8A8 SubCE8A8_OnNonzero
E8B6 SubCE8B6_Loop
E8CD SubCE8CD_Loop
E8D2 SubCE8D2_Loop
E8D7 SubCE8D7_Loop
E8E2 SubCE8E2_Loop
E8E9 SubCE8E9_Loop
E8FE SubCE8FE_Loop
E902 SubCE902_Loop
E903 SubCE903
E905 SubCE905_OnNonnegative
E918 SubCE918_Loop
E91A SubCE91A_OnNonzero
E91F SubCE91F
E921 SubCE921_OnNonnegative
E92E SubCE92E
E950 SubCE950_Loop
E95B SubCE95B_Loop
E95C SubCE95C
E95E SubCE95E_OnNonnegative
E969 SubCE969
E97E SubCE97E
E980 SubCE980_OnNonnegative
E992 SubCE992_Loop
E994 SubCE994_OnNonzero
E9A0 SubCE9A0_Loop
E9A9 SubCE9A9_Loop
E9B3 SubCE9B3_Loop
E9BC SubCE9BC
E9BE SubCE9BE_OnNonzero
E9CE SubCE9CE_Loop
EAC0 SubCEAC0_OnNonzero
EAC4 SubCEAC4
EACE SubCEACE_Loop
EAD6 SubCEAD6_Loop
EADB SubCEADB_Loop
EB0F SubCEB0F_Loop
EB18 SubCEB18_Loop
EB98 SubCEB98
EBAF SubCEBAF_Loop
EBBF SubCEBBF_Loop
EBC3 SubCEBC3_Loop
EC94 SubCEC94
EC9C SubCEC9C
ED21 SubCED21
ED26 SubCED26
ED30 SubCED30_OnNonzero
ED42 SubCED42
ED51 SubCED51
ED55 SubCED55_OnNonzero
ED60 SubCED60_Loop
ED65 SubCED65_Loop
ED66 SubCED66
ED8A SubCED8A_Loop
ED8C SubCED8C_OnZero
ED8D SubCED8D_OnZero
EDA7 SubCEDA7_Loop
EDAE SubCEDAE_Loop
EDB3 SubCEDB3
EDC0 SubCEDC0
EDD3 SubCEDD3_Loop
EDDD SubCEDDD_Loop
EDE7 SubCEDE7
EDF3 SubCEDF3
EDFA SubCEDFA_Loop
EDFE SubCEDFE
EE0A SubCEE0A
EE1D SubCEE1D_Loop
EE27 SubCEE27_Loop
EE28 SubCEE28
EE4E SubCEE4E_Loop
EE59 SubCEE59_Loop
EEC2 SubCEEC2
EED0 SubCEED0
EED9 SubCEED9
EEE9 SubCEEE9_Loop
EEEA SubCEEEA_Loop
EEFF SubCEEFF_Loop
EF09 SubCEF09_Loop
EF0E SubCEF0E_OnNonnegative
EF2F SubCEF2F_Loop
EF38 SubCEF38_Loop
EF3A SubCEF3A_Loop
EF3D SubCEF3D_Loop
EF53 SubCEF53
EF6F SubCEF6F_Loop
EF74 SubCEF74
EF76 SubCEF76_OnNonnegative
EF80 SubCEF80_Loop
F06E SubCF06E
F078 SubCF078
F07A SubCF07A_OnNonnegative
F084 SubCF084_OnZero
F085 SubCF085_Loop
F188 SubCF188
F196 SubCF196_OnNonnegative
F1A0 SubCF1A0_Loop
F1CF SubCF1CF
F1DF SubCF1DF_Loop
F1ED SubCF1ED_Loop
F1F3 SubCF1F3_Loop
F1F9 SubCF1F9_OnNonzero
F202 SubCF202_Loop
F215 SubCF215_Loop
F21F SubCF21F_Loop
F23F SubCF23F
F257 SubCF257_Loop
F267 SubCF267_Loop
F27A SubCF27A_Loop
F27E SubCF27E_Loop
F288 SubCF288_Loop
F290 SubCF290_Loop
F2A0 SubCF2A0_Loop
F2B3 SubCF2B3_Loop
F2B7 SubCF2B7_Loop
F2BE SubCF2BE_Loop
F2D6 SubCF2D6_Loop
F2D8 SubCF2D8_Loop
F2DB SubCF2DB
F2FB SubCF2FB_OnNonzero
F313 SubCF313_Loop
F315 SubCF315_Loop
F319 SubCF319_Loop
F31B SubCF31B_Loop
F31F SubCF31F_OnZero
F342 SubCF342
F34D SubCF34D_Loop
F356 SubCF356_Loop
F36D SubCF36D
F383 SubCF383_Loop
F386 SubCF386_Loop
F395 SubCF395_Loop
F39A SubCF39A
F3AA SubCF3AA_Loop
F3AD SubCF3AD_Loop
F3AF SubCF3AF_Loop
F3B0 SubCF3B0
F3C0 SubCF3C0_Loop
F3C3 SubCF3C3
F3D4 SubCF3D4
F3F4 SubCF3F4_Loop
F404 SubCF404_OnZero
F408 SubCF408
F415 SubCF415_Loop
F41F SubCF41F_Loop
F42D SubCF42D_Loop
F42E SubCF42E
F432 SubCF432
F434 SubCF434_Loop
F44B SubCF44B_Loop
F44E SubCF44E_OnCarrySet
F45F SubCF45F_Loop
F474 SubCF474_Loop
F479 SubCF479
F495 SubCF495_Loop
F4A6 SubCF4A6_Loop
F4BB SubCF4BB_Loop
F4BD SubCF4BD_Loop
F4BE SubCF4BE_Loop
F4DE SubCF4DE_Loop
F4F3 SubCF4F3_Loop
F4F5 SubCF4F5_Loop
F504 SubCF504_Loop
F51D SubCF51D
F535 SubCF535_Loop
F53F SubCF53F_OnZero
F540 SubCF540
F54E SubCF54E_Loop
F55D SubCF55D_Loop
F55F SubCF55F_Loop
F570 SubCF570_Loop
F571 SubCF571
F57A SubCF57A_OnNonzero
F587 SubCF587_Loop
F588 SubCF588_Loop
F599 SubCF599_Loop
F59A SubCF59A_Loop
F5A1 SubCF5A1_OnNonzero
F5BF SubCF5BF_Loop
F5C6 SubCF5C6
F5CD SubCF5CD_OnNonnegative
F5D8 SubCF5D8_Loop
F5FB SubCF5FB_Loop
F600 SubCF600_OnCarryClear
F601 SubCF601
F612 SubCF612
F61A SubCF61A_OnNonnegative
F62A SubCF62A_Loop
F633 SubCF633_Loop
F63A SubCF63A_Loop
F63F SubCF63F_Loop
F641 SubCF641_Loop
F649 SubCF649
F666 SubCF666
F671 SubCF671_OnZero
F672 SubCF672_OnCarryClear
F68D SubCF68D_Loop
F693 SubCF693_Loop
F6B6 SubCF6B6_OnZero
F6CD SubCF6CD
F6D7 SubCF6D7_Loop
F6DD SubCF6DD_Loop
F6E3 SubCF6E3_Loop
F6EE SubCF6EE_OnCarrySet
F6EF SubCF6EF_Loop
F70C SubCF70C_Loop
F726 SubCF726_Loop
F735 SubCF735_OnNonnegative
F758 SubCF758
F7DA SubCF7DA
F7DF SubCF7DF
F7E4 SubCF7E4
F7E9 SubCF7E9
F7EE SubCF7EE
F7FC SubCF7FC
F80C SubCF80C_Loop
F80D SubCF80D
F835 SubCF835_Loop
F85B SubCF85B_Loop
F85D SubCF85D_Loop
F867 SubCF867_Loop
F873 SubCF873_Loop
F87C SubCF87C
F880 SubCF880_OnCarryClear
F88B SubCF88B_Loop
F895 SubCF895_Loop
F89E SubCF89E_OnNonnegative
F8A9 SubCF8A9_Loop
F8AD SubCF8AD_OnZero
F8C4 SubCF8C4_OnNonzero
F8C8 SubCF8C8
F8E1 SubCF8E1
F8EE SubCF8EE_Loop
F8EF SubCF8EF_Loop
F8F2 SubCF8F2_Loop
F902 SubCF902_Loop
F918 SubCF918_Loop
F921 SubCF921_Loop
F93C SubCF93C_Loop
F955 SubCF955_Loop
F962 SubCF962_Loop
F975 SubCF975
F97A SubCF97A_Loop
F981 SubCF981_Loop
F987 SubCF987_Loop
F994 SubCF994_Loop
F99B SubCF99B_Loop
F9AE SubCF9AE_Loop
F9B3 SubCF9B3_Loop
F9BD SubCF9BD_Loop
F9C9 SubCF9C9
F9D1 SubCF9D1_Loop
F9FF SubCF9FF_Loop
FA12 SubCFA12_Loop
FA23 SubCFA23_Loop
FA32 SubCFA32_OnNonzero
FA3A SubCFA3A_Loop
FA3C SubCFA3C_Loop
FA5E SubCFA5E_Loop
FA62 SubCFA62_Loop
FA73 SubCFA73
FA80 SubCFA80_Loop
FA98 SubCFA98_Loop
FA9A SubCFA9A_Loop
FAA1 SubCFAA1_Loop
FAA9 SubCFAA9
FABA SubCFABA_Loop