Files
disasm/NROM/Hydlide (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

960 lines
17 KiB
Plaintext

8000 Reset
8003 NmiHandler
801A SubC801A
820E SubC820E
8210 SubC8210
836C SubC836C
85E0 SubC85E0
8615 SubC8615
8629 SubC8629
865D SubC865D
86B4 SubC86B4
86E9 SubC86E9
8760 SubC8760
877A SubC877A
8782 SubC8782
8804 SubC8804
8825 SubC8825
8867 SubC8867
8893 SubC8893
88EF SubC88EF
891C SubC891C
8952 SubC8952
8974 SubC8974
89D4 SubC89D4
89DC SubC89DC
89E6 SubC89E6
89F0 SubC89F0
8A06 SubC8A06
8A10 SubC8A10
8A3B SubC8A3B
8AE8 SubC8AE8
8AF9 SubC8AF9
8B08 SubC8B08
8B19 SubC8B19
8B27 SubC8B27
8B38 SubC8B38
8DCD SubC8DCD
8E20 SubC8E20
8E34 SubC8E34
8E41 SubC8E41
8E88 SubC8E88
8EA3 SubC8EA3
8EE5 SubC8EE5
8F02 SubC8F02
8F06 SubC8F06
8F41 SubC8F41
90F6 SubC90F6
9124 SubC9124
9144 SubC9144
919D SubC919D
91BF SubC91BF
91D5 SubC91D5
927F SubC927F
9289 SubC9289
9297 SubC9297
92A1 SubC92A1
92AF SubC92AF
92E8 SubC92E8
9326 SubC9326
937A SubC937A
94A6 SubC94A6
9534 SubC9534
9574 SubC9574
957E SubC957E
95A1 SubC95A1
95F4 SubC95F4
9600 SubC9600
9604 SubC9604
961F SubC961F
9636 SubC9636
9639 SubC9639
963C SubC963C
965A SubC965A
965D SubC965D
9672 SubC9672
967D SubC967D
968E SubC968E
96C0 SubC96C0
96CA SubC96CA
96E4 SubC96E4
9733 SubC9733
9742 SubC9742
9751 SubC9751
9757 SubC9757
975D SubC975D
9792 SubC9792
9A76 SubC9A76
9B35 SubC9B35
9BB0 SubC9BB0
9D07 SubC9D07
9D64 SubC9D64
9EA4 SubC9EA4
9EA7 SubC9EA7
9F34 SubC9F34
9F7F SubC9F7F
A011 SubCA011
A053 SubCA053
A070 SubCA070
A0A6 SubCA0A6
A122 SubCA122
A158 SubCA158
A174 SubCA174
A177 SubCA177
A196 SubCA196
A1BD SubCA1BD
A1EE SubCA1EE
A255 SubCA255
A2EB SubCA2EB
A397 SubCA397
A40E SubCA40E
A43B SubCA43B
A46B SubCA46B
A49D SubCA49D
A4CB SubCA4CB
A4E3 SubCA4E3
A50A SubCA50A
A57E SubCA57E
A5C1 SubCA5C1
A5EF SubCA5EF
A60D SubCA60D
A67E SubCA67E
A76C SubCA76C
A780 SubCA780
A82E SubCA82E
A927 SubCA927
AB5A SubCAB5A
ABF7 SubCABF7
AC14 SubCAC14
AC53 SubCAC53
AE22 SubCAE22
AE97 SubCAE97
AEB3 SubCAEB3
AF46 SubCAF46
AF7E SubCAF7E
B082 SubCB082
B08D SubCB08D
B22F SubCB22F
B272 SubCB272
B315 SubCB315
B337 SubCB337
B386 SubCB386
B3D3 SubCB3D3
B400 SubCB400
B4DD SubCB4DD
B50B SubCB50B
B694 SubCB694
B902 SubCB902
B90D SubCB90D
BAF2 SubCBAF2
BFDF SubCBFDF
C097 SubCC097
C79E SubCC79E
C7C1 SubCC7C1
C86D SubCC86D
C875 SubCC875
C884 SubCC884
C8F9 SubCC8F9
C99A SubCC99A
C9D1 SubCC9D1
CA9B SubCCA9B
CAA4 SubCCAA4
CAE6 SubCCAE6
CB35 SubCCB35
CB4D SubCCB4D
CB6B SubCCB6B
CBBD SubCCBBD
CC7B SubCCC7B
CE8C SubCCE8C
CE8F SubCCE8F
CEE1 SubCCEE1
CF46 SubCCF46
CF77 SubCCF77
D144 SubCD144
D14C SubCD14C
D154 SubCD154
D4BB SubCD4BB
D550 SubCD550
D5FA SubCD5FA
DAC4 SubCDAC4
DBD3 SubCDBD3
DD68 SubCDD68
DD75 SubCDD75
DDCB SubCDDCB
DE51 SubCDE51
DE6E SubCDE6E
DEB9 SubCDEB9
DF11 SubCDF11
DF51 SubCDF51
E142 SubCE142
E1C2 SubCE1C2
E1D3 SubCE1D3
E21B SubCE21B
E265 SubCE265
E26B SubCE26B
E271 SubCE271
E293 SubCE293
E2C4 SubCE2C4
E2C9 SubCE2C9
# ---- derived internal branch-target names ----
8000 Reset
8003 NmiHandler
800F SubC800F_Loop
801A SubC801A
8024 SubC8024_OnNonnegative
8029 SubC8029_OnNonnegative
8084 SubC8084_OnNonzero
8094 SubC8094_Loop
8098 SubC8098_OnNonzero
80A6 SubC80A6_OnNonzero
80A8 SubC80A8_OnNonzero
80B4 SubC80B4_OnNonzero
80DB SubC80DB_OnNonzero
80F5 SubC80F5_OnNonzero
810A SubC810A_OnNonzero
8114 SubC8114_OnNonzero
8176 SubC8176_OnNonzero
81F5 SubC81F5_OnNonzero
820B SubC820B_Loop
820E SubC820E
8210 SubC8210
8231 SubC8231_OnNonzero
824B SubC824B_OnNonzero
8260 SubC8260_OnNonzero
826A SubC826A_OnNonzero
82D7 SubC82D7_OnNonzero
82F1 SubC82F1_OnNonzero
830E SubC830E_OnNonzero
836C SubC836C
8388 SubC8388_OnNonzero
838F SubC838F_OnNonzero
83AD SubC83AD_Loop
83C0 SubC83C0_OnNonzero
85E0 SubC85E0
85E7 SubC85E7_OnNonzero
8615 SubC8615
8629 SubC8629
8630 SubC8630_OnNonzero
865D SubC865D
86B4 SubC86B4
86E6 SubC86E6_Loop
86E9 SubC86E9
86FA SubC86FA_Loop
8715 SubC8715_Loop
871B SubC871B_OnZero
871E SubC871E_Loop
8735 SubC8735_Loop
873E SubC873E_Loop
8753 SubC8753_Loop
875C SubC875C_Loop
875E SubC875E_Loop
8760 SubC8760
8776 SubC8776_Loop
877A SubC877A
8782 SubC8782
87A1 SubC87A1_Loop
87A9 SubC87A9_Loop
87AF SubC87AF_Loop
87B8 SubC87B8_Loop
87C1 SubC87C1_Loop
87CA SubC87CA_Loop
87D3 SubC87D3_Loop
87DC SubC87DC_Loop
87E5 SubC87E5_Loop
87F3 SubC87F3_Loop
87FC SubC87FC_Loop
8803 SubC8803_Loop
8804 SubC8804
8825 SubC8825
882A SubC882A_Loop
882B SubC882B_Loop
8841 SubC8841_Loop
8847 SubC8847_Loop
8857 SubC8857_Loop
885F SubC885F_Loop
8867 SubC8867
8893 SubC8893
8898 SubC8898_Loop
8899 SubC8899_Loop
88AB SubC88AB_Loop
88B1 SubC88B1_Loop
88C5 SubC88C5_Loop
88CD SubC88CD_Loop
88E7 SubC88E7_Loop
88EF SubC88EF
891C SubC891C
8921 SubC8921_Loop
8922 SubC8922_Loop
8934 SubC8934_Loop
893A SubC893A_Loop
8946 SubC8946_Loop
8952 SubC8952
8974 SubC8974
8979 SubC8979_Loop
897A SubC897A_Loop
8990 SubC8990_Loop
8996 SubC8996_Loop
89BC SubC89BC_Loop
89C4 SubC89C4_Loop
89D4 SubC89D4
89DC SubC89DC
89E6 SubC89E6
89F0 SubC89F0
89F8 SubC89F8_Loop
8A06 SubC8A06
8A10 SubC8A10
8A18 SubC8A18_Loop
8A24 SubC8A24_Loop
8A3A SubC8A3A_Loop
8A3B SubC8A3B
8A43 SubC8A43_OnNonzero
8A44 SubC8A44_Loop
8A7A SubC8A7A_Loop
8A81 SubC8A81_Loop
8A88 SubC8A88_Loop
8A8B SubC8A8B_Loop
8A94 SubC8A94_Loop
8A9D SubC8A9D_Loop
8AA6 SubC8AA6_Loop
8AAF SubC8AAF_Loop
8ABE SubC8ABE_Loop
8AC7 SubC8AC7_Loop
8AD0 SubC8AD0_Loop
8AD9 SubC8AD9_Loop
8AE8 SubC8AE8
8AF9 SubC8AF9
8B08 SubC8B08
8B19 SubC8B19
8B27 SubC8B27
8B38 SubC8B38
8DCD SubC8DCD
8DDC SubC8DDC_Loop
8E20 SubC8E20
8E34 SubC8E34
8E41 SubC8E41
8E43 SubC8E43_Loop
8E88 SubC8E88
8EA3 SubC8EA3
8EC7 SubC8EC7_Loop
8ECA SubC8ECA_Loop
8ECB SubC8ECB_Loop
8EDA SubC8EDA_Loop
8EDD SubC8EDD_Loop
8EE2 SubC8EE2_Loop
8EE5 SubC8EE5
8EFA SubC8EFA_Loop
8F00 SubC8F00_Loop
8F02 SubC8F02
8F06 SubC8F06
8F0B SubC8F0B_Loop
8F17 SubC8F17_OnNegative
8F2B SubC8F2B_Loop
8F41 SubC8F41
8F4B SubC8F4B_Loop
8F4E SubC8F4E_Loop
8F5F SubC8F5F_Loop
8F65 SubC8F65_Loop
8F71 SubC8F71_Loop
8F7F SubC8F7F_Loop
8F81 SubC8F81_Loop
8F89 SubC8F89_Loop
8F9C SubC8F9C_Loop
8FA2 SubC8FA2_Loop
8FAB SubC8FAB_Loop
8FCB SubC8FCB_Loop
8FD8 SubC8FD8_Loop
8FE5 SubC8FE5_Loop
8FF1 SubC8FF1_Loop
8FFE SubC8FFE_Loop
900B SubC900B_Loop
9016 SubC9016_Loop
9027 SubC9027_Loop
903B SubC903B_Loop
9067 SubC9067_Loop
9082 SubC9082_Loop
9097 SubC9097_Loop
90A9 SubC90A9_Loop
90B2 SubC90B2_Loop
90C4 SubC90C4_Loop
90D6 SubC90D6_Loop
90E2 SubC90E2_Loop
90F5 SubC90F5_Loop
90F6 SubC90F6
911C SubC911C_Loop
911D SubC911D_Loop
9124 SubC9124
9142 SubC9142_Loop
9144 SubC9144
915B SubC915B_Loop
915F SubC915F_OnNonzero
916D SubC916D_Loop
916F SubC916F_Loop
9174 SubC9174_OnNonzero
918B SubC918B_Loop
9191 SubC9191_Loop
9199 SubC9199_Loop
919D SubC919D
91BF SubC91BF
91C9 SubC91C9_Loop
91D5 SubC91D5
924B SubC924B_Loop
927C SubC927C_Loop
927F SubC927F
9289 SubC9289
9297 SubC9297
92A1 SubC92A1
92AF SubC92AF
92E8 SubC92E8
9326 SubC9326
932C SubC932C_Loop
9379 SubC9379_Loop
937A SubC937A
93A8 SubC93A8_Loop
93D6 SubC93D6_OnNonzero
9446 SubC9446_OnNonzero
94A6 SubC94A6
951A SubC951A_OnZero
9521 SubC9521_Loop
952B SubC952B_OnZero
9534 SubC9534
9545 SubC9545_Loop
9549 SubC9549_OnNonzero
9574 SubC9574
9576 SubC9576_OnNonzero
957E SubC957E
958A SubC958A_OnNonzero
9598 SubC9598_Loop
95A1 SubC95A1
95D7 SubC95D7_Loop
95E5 SubC95E5_Loop
95F4 SubC95F4
9600 SubC9600
9604 SubC9604
961F SubC961F
9636 SubC9636
9639 SubC9639
963C SubC963C
9643 SubC9643_OnNonzero
965A SubC965A
965D SubC965D
9672 SubC9672
967D SubC967D
9681 SubC9681_OnCarryClear
968E SubC968E
96C0 SubC96C0
96C9 SubC96C9_Loop
96CA SubC96CA
96E4 SubC96E4
96E8 SubC96E8_OnNonzero
96FF SubC96FF_OnNonzero
9706 SubC9706_OnNonzero
972B SubC972B_Loop
9733 SubC9733
9742 SubC9742
9751 SubC9751
9757 SubC9757
975D SubC975D
976A SubC976A_Loop
9772 SubC9772_OnNonzero
977F SubC977F_Loop
9788 SubC9788_Loop
978A SubC978A_Loop
9792 SubC9792
9A76 SubC9A76
9A81 SubC9A81_Loop
9A89 SubC9A89_Loop
9AB0 SubC9AB0_Loop
9ABC SubC9ABC_Loop
9AC2 SubC9AC2_Loop
9AC9 SubC9AC9_Loop
9AD5 SubC9AD5_Loop
9AF2 SubC9AF2_Loop
9AFB SubC9AFB_Loop
9B05 SubC9B05_Loop
9B0D SubC9B0D_Loop
9B1A SubC9B1A_Loop
9B20 SubC9B20_Loop
9B26 SubC9B26_Loop
9B2C SubC9B2C_Loop
9B32 SubC9B32_Loop
9B35 SubC9B35
9B40 SubC9B40_OnNonzero
9B56 SubC9B56_OnNegative
9B77 SubC9B77_Loop
9B85 SubC9B85_Loop
9BA9 SubC9BA9_Loop
9BB0 SubC9BB0
9BD4 SubC9BD4_Loop
9BDF SubC9BDF_Loop
9BEB SubC9BEB_Loop
9BF9 SubC9BF9_Loop
9C07 SubC9C07_Loop
9C15 SubC9C15_Loop
9C23 SubC9C23_Loop
9C52 SubC9C52_Loop
9C5E SubC9C5E_Loop
9C61 SubC9C61_Loop
9C7D SubC9C7D_Loop
9C84 SubC9C84_Loop
9C90 SubC9C90_OnNegative
9CB1 SubC9CB1_Loop
9CC9 SubC9CC9_Loop
9CEA SubC9CEA_Loop
9CEC SubC9CEC_Loop
9CFB SubC9CFB_Loop
9D04 SubC9D04_Loop
9D07 SubC9D07
9D1D SubC9D1D_OnNonzero
9D61 SubC9D61_Loop
9D64 SubC9D64
9D88 SubC9D88_Loop
9D93 SubC9D93_Loop
9D9F SubC9D9F_Loop
9DAD SubC9DAD_Loop
9DBB SubC9DBB_Loop
9DC9 SubC9DC9_Loop
9DD7 SubC9DD7_Loop
9DFE SubC9DFE_Loop
9E0A SubC9E0A_Loop
9E0D SubC9E0D_Loop
9E29 SubC9E29_Loop
9E35 SubC9E35_OnNegative
9E56 SubC9E56_Loop
9E6E SubC9E6E_Loop
9E87 SubC9E87_Loop
9E89 SubC9E89_Loop
9E98 SubC9E98_Loop
9EA1 SubC9EA1_Loop
9EA4 SubC9EA4
9EA7 SubC9EA7
9EB0 SubC9EB0_Loop
9ED9 SubC9ED9_Loop
9EE1 SubC9EE1_Loop
9EE8 SubC9EE8_Loop
9EF6 SubC9EF6_Loop
9F04 SubC9F04_Loop
9F34 SubC9F34
9F7F SubC9F7F
9F8C SubC9F8C_Loop
9F98 SubC9F98_Loop
9F9B SubC9F9B_Loop
9FC1 SubC9FC1_Loop
9FCD SubC9FCD_OnNegative
9FF9 SubC9FF9_Loop
A011 SubCA011
A026 SubCA026_Loop
A028 SubCA028_Loop
A037 SubCA037_Loop
A045 SubCA045_Loop
A04D SubCA04D_Loop
A050 SubCA050_Loop
A053 SubCA053
A070 SubCA070
A074 SubCA074_OnNonzero
A09A SubCA09A_Loop
A0A3 SubCA0A3_Loop
A0A6 SubCA0A6
A0B1 SubCA0B1_OnNonzero
A0C5 SubCA0C5_Loop
A0D9 SubCA0D9_Loop
A0E9 SubCA0E9_OnNegative
A10A SubCA10A_Loop
A122 SubCA122
A13B SubCA13B_Loop
A13D SubCA13D_Loop
A14C SubCA14C_Loop
A155 SubCA155_Loop
A158 SubCA158
A174 SubCA174
A177 SubCA177
A17B SubCA17B_OnNonzero
A196 SubCA196
A1BD SubCA1BD
A1E1 SubCA1E1_Loop
A1EE SubCA1EE
A245 SubCA245_Loop
A255 SubCA255
A284 SubCA284_OnNonzero
A28E SubCA28E_OnNonzero
A296 SubCA296_OnNonzero
A2CF SubCA2CF_OnNonzero
A2E6 SubCA2E6_Loop
A2EB SubCA2EB
A2F0 SubCA2F0_Loop
A388 SubCA388_OnNonzero
A397 SubCA397
A3A7 SubCA3A7_OnZero
A3BE SubCA3BE_Loop
A3C8 SubCA3C8_Loop
A3D4 SubCA3D4_Loop
A3D7 SubCA3D7_Loop
A3E3 SubCA3E3_Loop
A3E6 SubCA3E6_Loop
A3EF SubCA3EF_Loop
A3F6 SubCA3F6_Loop
A3FD SubCA3FD_Loop
A404 SubCA404_Loop
A40B SubCA40B_Loop
A40E SubCA40E
A41A SubCA41A_Loop
A423 SubCA423_OnCarrySet
A426 SubCA426_Loop
A428 SubCA428_OnNegative
A43B SubCA43B
A463 SubCA463_Loop
A46B SubCA46B
A48A SubCA48A_OnNonzero
A49D SubCA49D
A4AD SubCA4AD_OnZero
A4C1 SubCA4C1_Loop
A4CB SubCA4CB
A4D4 SubCA4D4_Loop
A4D9 SubCA4D9_Loop
A4E1 SubCA4E1_Loop
A4E3 SubCA4E3
A4EF SubCA4EF_Loop
A4F4 SubCA4F4_OnNegative
A50A SubCA50A
A55A SubCA55A_OnNegative
A565 SubCA565_OnNonzero
A570 SubCA570_OnZero
A57E SubCA57E
A5A9 SubCA5A9_OnNonzero
A5BF SubCA5BF_Loop
A5C1 SubCA5C1
A5D1 SubCA5D1_OnZero
A5E5 SubCA5E5_Loop
A5EF SubCA5EF
A5F8 SubCA5F8_Loop
A5FD SubCA5FD_Loop
A606 SubCA606_Loop
A60D SubCA60D
A60F SubCA60F_OnNonzero
A62A SubCA62A_OnNonzero
A635 SubCA635_OnNonzero
A663 SubCA663_OnNegative
A67E SubCA67E
A69C SubCA69C_OnNegative
A6E5 SubCA6E5_Loop
A6F8 SubCA6F8_Loop
A703 SubCA703_Loop
A70E SubCA70E_Loop
A72C SubCA72C_OnNegative
A753 SubCA753_OnNonzero
A75E SubCA75E_OnZero
A76C SubCA76C
A780 SubCA780
A7A7 SubCA7A7_OnNonzero
A7B6 SubCA7B6_OnNonzero
A7C5 SubCA7C5_OnNonzero
A7DD SubCA7DD_Loop
A7F0 SubCA7F0_OnNonzero
A812 SubCA812_OnNonzero
A81C SubCA81C_OnNonzero
A82E SubCA82E
A837 SubCA837_Loop
A859 SubCA859_OnNonzero
A863 SubCA863_OnZero
A86D SubCA86D_OnNonzero
A927 SubCA927
A97D SubCA97D_OnNonzero
A9F4 SubCA9F4_OnNonzero
A9FE SubCA9FE_Loop
AA28 SubCAA28_OnNonzero
AA36 SubCAA36_OnNonzero
AA4C SubCAA4C_Loop
AA71 SubCAA71_OnNonzero
AA82 SubCAA82_OnNonzero
AA98 SubCAA98_Loop
AABD SubCAABD_OnNonnegative
AAD6 SubCAAD6_OnNonzero
AAE0 SubCAAE0_Loop
AAF9 SubCAAF9_OnNonzero
AB5A SubCAB5A
ABA2 SubCABA2_Loop
ABA6 SubCABA6_OnNonzero
ABE2 SubCABE2_OnZero
ABF7 SubCABF7
AC14 SubCAC14
AC24 SubCAC24_Loop
AC41 SubCAC41_Loop
AC4E SubCAC4E_Loop
AC53 SubCAC53
AC8F SubCAC8F_OnNonzero
ACF4 SubCACF4_OnNonzero
AD1C SubCAD1C_Loop
AD30 SubCAD30_OnZero
AD58 SubCAD58_Loop
AD75 SubCAD75_Loop
AD96 SubCAD96_Loop
ADAD SubCADAD_Loop
ADBB SubCADBB_Loop
ADE5 SubCADE5_Loop
AE0B SubCAE0B_Loop
AE1F SubCAE1F_Loop
AE22 SubCAE22
AE48 SubCAE48_Loop
AE51 SubCAE51_Loop
AE58 SubCAE58_Loop
AE62 SubCAE62_Loop
AE94 SubCAE94_Loop
AE97 SubCAE97
AEB0 SubCAEB0_Loop
AEB3 SubCAEB3
AEBC SubCAEBC_Loop
AED4 SubCAED4_OnNegative
AEED SubCAEED_Loop
AEFF SubCAEFF_OnNegative
AF0F SubCAF0F_OnNegative
AF1D SubCAF1D_Loop
AF29 SubCAF29_Loop
AF34 SubCAF34_OnNegative
AF46 SubCAF46
AF66 SubCAF66_Loop
AF7E SubCAF7E
AF96 SubCAF96_Loop
AF9F SubCAF9F_Loop
AFAD SubCAFAD_OnNonzero
B06F SubCB06F_OnNonzero
B07F SubCB07F_Loop
B082 SubCB082
B08D SubCB08D
B0A1 SubCB0A1_OnNonzero
B0DD SubCB0DD_OnNonzero
B0FD SubCB0FD_Loop
B107 SubCB107_OnZero
B127 SubCB127_Loop
B131 SubCB131_Loop
B13B SubCB13B_OnNonzero
B171 SubCB171_OnNonzero
B1A2 SubCB1A2_OnNonzero
B1EF SubCB1EF_OnNonzero
B22F SubCB22F
B252 SubCB252_Loop
B26D SubCB26D_Loop
B272 SubCB272
B290 SubCB290_OnNonnegative
B2AC SubCB2AC_OnNonzero
B2CB SubCB2CB_OnNonzero
B2D9 SubCB2D9_OnNegative
B2F5 SubCB2F5_OnNonzero
B315 SubCB315
B337 SubCB337
B37E SubCB37E_Loop
B386 SubCB386
B3C9 SubCB3C9_Loop
B3D3 SubCB3D3
B400 SubCB400
B4DD SubCB4DD
B4FD SubCB4FD_Loop
B50B SubCB50B
B513 SubCB513_Loop
B517 SubCB517_OnNonzero
B613 SubCB613_OnNegative
B633 SubCB633_Loop
B644 SubCB644_Loop
B64E SubCB64E_OnNegative
B65C SubCB65C_Loop
B66E SubCB66E_OnNegative
B67B SubCB67B_Loop
B686 SubCB686_OnNegative
B694 SubCB694
B698 SubCB698_OnNonzero
B6A2 SubCB6A2_OnNegative
B6AF SubCB6AF_Loop
B6B8 SubCB6B8_Loop
B6C2 SubCB6C2_OnNegative
B6CD SubCB6CD_Loop
B6DA SubCB6DA_OnNegative
B6E6 SubCB6E6_Loop
B6F0 SubCB6F0_Loop
B700 SubCB700_Loop
B70C SubCB70C_Loop
B716 SubCB716_OnNegative
B728 SubCB728_Loop
B730 SubCB730_Loop
B738 SubCB738_Loop
B740 SubCB740_Loop
B748 SubCB748_Loop
B760 SubCB760_Loop
B768 SubCB768_Loop
B77C SubCB77C_Loop
B790 SubCB790_Loop
B7A4 SubCB7A4_Loop
B7B8 SubCB7B8_Loop
B7CC SubCB7CC_Loop
B7E0 SubCB7E0_Loop
B7F4 SubCB7F4_Loop
B808 SubCB808_Loop
B81C SubCB81C_Loop
B830 SubCB830_Loop
B850 SubCB850_Loop
B856 SubCB856_Loop
B87C SubCB87C_OnNonzero
B88C SubCB88C_OnNonzero
B896 SubCB896_Loop
B8C8 SubCB8C8_Loop
B8D0 SubCB8D0_Loop
B8DA SubCB8DA_Loop
B8E2 SubCB8E2_Loop
B8EA SubCB8EA_Loop
B8F2 SubCB8F2_Loop
B8FA SubCB8FA_Loop
B900 SubCB900_Loop
B902 SubCB902
B90D SubCB90D
B93E SubCB93E_Loop
B942 SubCB942_OnNonzero
B952 SubCB952_Loop
BAF2 SubCBAF2
BB02 SubCBB02_OnNegative
BFDF SubCBFDF
C007 SubCC007_OnZero
C016 SubCC016_Loop
C018 SubCC018_OnNonzero
C027 SubCC027_Loop
C02B SubCC02B_Loop
C02F SubCC02F_Loop
C03B SubCC03B_OnZero
C04A SubCC04A_Loop
C04C SubCC04C_OnNonzero
C05B SubCC05B_Loop
C05F SubCC05F_Loop
C063 SubCC063_Loop
C06F SubCC06F_OnZero
C07E SubCC07E_Loop
C080 SubCC080_OnNonzero
C08F SubCC08F_Loop
C093 SubCC093_Loop
C097 SubCC097
C79E SubCC79E
C7C1 SubCC7C1
C7CC SubCC7CC_Loop
C7D7 SubCC7D7_Loop
C7E8 SubCC7E8_Loop
C86D SubCC86D
C874 SubCC874_Loop
C875 SubCC875
C884 SubCC884
C8BB SubCC8BB_Loop
C8C2 SubCC8C2_OnNonzero
C8C8 SubCC8C8_Loop
C8C9 SubCC8C9_Loop
C8D3 SubCC8D3_Loop
C8DA SubCC8DA_Loop
C8E4 SubCC8E4_Loop
C8F9 SubCC8F9
C930 SubCC930_Loop
C937 SubCC937_OnNonzero
C93D SubCC93D_Loop
C93E SubCC93E_Loop
C948 SubCC948_Loop
C94F SubCC94F_Loop
C959 SubCC959_Loop
C99A SubCC99A
C9C0 SubCC9C0_Loop
C9C2 SubCC9C2_OnNegative
C9D1 SubCC9D1
CA01 SubCCA01_Loop
CA08 SubCCA08_Loop
CA0F SubCCA0F_Loop
CA16 SubCCA16_Loop
CA24 SubCCA24_Loop
CA55 SubCCA55_Loop
CA74 SubCCA74_Loop
CA9B SubCCA9B
CAA4 SubCCAA4
CAB3 SubCCAB3_Loop
CAE6 SubCCAE6
CAF8 SubCCAF8_Loop
CB11 SubCCB11_Loop
CB35 SubCCB35
CB4D SubCCB4D
CB4F SubCCB4F_OnNegative
CB62 SubCCB62_Loop
CB6B SubCCB6B
CBBD SubCCBBD
CBC7 SubCCBC7_Loop
CBCA SubCCBCA_Loop
CC7B SubCCC7B
CE8C SubCCE8C
CE8F SubCCE8F
CEE1 SubCCEE1
CF46 SubCCF46
CF52 SubCCF52_OnNegative
CF61 SubCCF61_Loop
CF77 SubCCF77
D144 SubCD144
D14C SubCD14C
D154 SubCD154
D172 SubCD172_Loop
D4BB SubCD4BB
D4BD SubCD4BD_OnNonzero
D4C6 SubCD4C6_OnNonzero
D4EB SubCD4EB_OnNonzero
D4F1 SubCD4F1_OnNonzero
D50E SubCD50E_Loop
D524 SubCD524_OnNegative
D52E SubCD52E_Loop
D536 SubCD536_Loop
D540 SubCD540_OnNonzero
D550 SubCD550
D560 SubCD560_Loop
D58C SubCD58C_Loop
D5EB SubCD5EB_Loop
D5F9 SubCD5F9_Loop
D5FA SubCD5FA
DAC4 SubCDAC4
DAD4 SubCDAD4_OnNegative
DADE SubCDADE_OnNegative
DAE8 SubCDAE8_OnNegative
DB37 SubCDB37_OnNegative
DB73 SubCDB73_Loop
DB80 SubCDB80_Loop
DB88 SubCDB88_Loop
DBB9 SubCDBB9_OnNonzero
DBD3 SubCDBD3
DBD7 SubCDBD7_OnNonzero
DC13 SubCDC13_Loop
DC20 SubCDC20_Loop
DC28 SubCDC28_Loop
DC73 SubCDC73_OnNonzero
DD68 SubCDD68
DD75 SubCDD75
DD7B SubCDD7B_OnNegative
DD88 SubCDD88_OnNegative
DD95 SubCDD95_OnNonzero
DDA2 SubCDDA2_OnNonzero
DDC6 SubCDDC6_Loop
DDCB SubCDDCB
DE15 SubCDE15_Loop
DE51 SubCDE51
DE5D SubCDE5D_Loop
DE6E SubCDE6E
DE70 SubCDE70_OnNonzero
DE80 SubCDE80_OnNonzero
DEB9 SubCDEB9
DF11 SubCDF11
DF2C SubCDF2C_OnNegative
DF51 SubCDF51
DF6C SubCDF6C_OnNegative
E142 SubCE142
E14D SubCE14D_Loop
E1C2 SubCE1C2
E1D0 SubCE1D0_Loop
E1D3 SubCE1D3
E1F9 SubCE1F9_Loop
E218 SubCE218_Loop
E21B SubCE21B
E241 SubCE241_Loop
E262 SubCE262_Loop
E265 SubCE265
E26B SubCE26B
E271 SubCE271
E277 SubCE277_Loop
E293 SubCE293
E299 SubCE299_Loop
E2C4 SubCE2C4
E2C9 SubCE2C9