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

962 lines
16 KiB
Plaintext

8000 Reset
806F SubC806F
8079 NmiHandler
80DD SubC80DD
8163 SubC8163
8331 SubC8331
834D SubC834D
8351 SubC8351
835C SubC835C
8365 SubC8365
836C SubC836C
838C SubC838C
857B SubC857B
87BA SubC87BA
87F1 SubC87F1
8825 SubC8825
8859 SubC8859
88D9 SubC88D9
88E7 SubC88E7
88F5 SubC88F5
8900 SubC8900
890D SubC890D
891A SubC891A
8959 SubC8959
8960 SubC8960
89BF SubC89BF
8A5B SubC8A5B
8A72 SubC8A72
8A81 SubC8A81
8A8C SubC8A8C
8A9F SubC8A9F
8D04 SubC8D04
8D3E SubC8D3E
8D4E SubC8D4E
8D87 SubC8D87
8DE5 SubC8DE5
8E21 SubC8E21
8E55 SubC8E55
8E8F SubC8E8F
8E9C SubC8E9C
8EE2 SubC8EE2
8EFA SubC8EFA
8FAA SubC8FAA
8FE3 SubC8FE3
9096 SubC9096
911E SubC911E
9143 SubC9143
916E SubC916E
918B SubC918B
91A8 SubC91A8
91E1 SubC91E1
9229 SubC9229
922B SubC922B
92FB SubC92FB
936A SubC936A
93BA SubC93BA
93FD SubC93FD
9426 SubC9426
9469 SubC9469
9471 SubC9471
9512 SubC9512
95B6 SubC95B6
9608 SubC9608
9631 SubC9631
965A SubC965A
9677 SubC9677
9694 SubC9694
96AA SubC96AA
96E9 SubC96E9
977D SubC977D
97D4 SubC97D4
980F SubC980F
9884 SubC9884
98FD SubC98FD
99C6 SubC99C6
9A5C SubC9A5C
A07E SubCA07E
A0E1 SubCA0E1
A165 SubCA165
A18F SubCA18F
A1BA SubCA1BA
A1D5 SubCA1D5
A1F0 SubCA1F0
A252 SubCA252
A2B4 SubCA2B4
A2D9 SubCA2D9
A2FF SubCA2FF
A318 SubCA318
A37F SubCA37F
A40F SubCA40F
A443 SubCA443
A47E SubCA47E
A488 SubCA488
A4A5 SubCA4A5
A4C2 SubCA4C2
A4CD SubCA4CD
A52F SubCA52F
A581 SubCA581
A679 SubCA679
A764 SubCA764
A793 SubCA793
A7D7 SubCA7D7
A8D3 SubCA8D3
A8DC SubCA8DC
A908 SubCA908
A940 SubCA940
A9CC SubCA9CC
AA22 SubCAA22
AA4E SubCAA4E
AA7B SubCAA7B
AA95 SubCAA95
AAC1 SubCAAC1
AADB SubCAADB
AB6F SubCAB6F
ABA0 SubCABA0
AC23 SubCAC23
AC3F SubCAC3F
AC77 SubCAC77
ACB0 SubCACB0
ACC1 SubCACC1
ACEB SubCACEB
ACFC SubCACFC
AD54 SubCAD54
ADFF SubCADFF
AE01 SubCAE01
AE87 SubCAE87
AF14 SubCAF14
AF22 SubCAF22
AF4A SubCAF4A
AF94 SubCAF94
AFD8 SubCAFD8
AFDF SubCAFDF
B02A SubCB02A
B04B SubCB04B
B069 SubCB069
B095 SubCB095
B0EA SubCB0EA
B0F4 SubCB0F4
B104 SubCB104
B15C SubCB15C
B16D SubCB16D
B17C SubCB17C
B19D SubCB19D
B1BF SubCB1BF
B1DA SubCB1DA
B1F8 SubCB1F8
B20A SubCB20A
B220 SubCB220
B230 SubCB230
B239 SubCB239
B244 SubCB244
B28B SubCB28B
B29B SubCB29B
B29F SubCB29F
B2A3 SubCB2A3
B2A7 SubCB2A7
B2AB SubCB2AB
B2AF SubCB2AF
B2B3 SubCB2B3
B2B7 SubCB2B7
B2C2 SubCB2C2
B2D5 SubCB2D5
B2DD SubCB2DD
B2E5 SubCB2E5
B2E9 SubCB2E9
B2F1 SubCB2F1
B2FC SubCB2FC
B300 SubCB300
B308 SubCB308
B30C SubCB30C
B310 SubCB310
B314 SubCB314
B31B SubCB31B
B33C SubCB33C
B345 SubCB345
B346 SubCB346
B347 SubCB347
B34C SubCB34C
B352 SubCB352
B357 SubCB357
B359 SubCB359
F0A0 SubCF0A0
F0A4 SubCF0A4
F0A8 SubCF0A8
F0AC SubCF0AC
F0C5 SubCF0C5
F112 SubCF112
F11A SubCF11A
F123 SubCF123
F150 SubCF150
F180 SubCF180
F194 SubCF194
F1DE SubCF1DE
F225 SubCF225
F248 SubCF248
F2E2 SubCF2E2
F305 SubCF305
F337 SubCF337
F353 SubCF353
F3AA SubCF3AA
F3CC SubCF3CC
F3DF SubCF3DF
F44F SubCF44F
F4C0 SubCF4C0
F537 SubCF537
F5CB SubCF5CB
F5E8 SubCF5E8
F690 SubCF690
F6CB SubCF6CB
F704 SubCF704
F77D SubCF77D
F794 SubCF794
F7A6 SubCF7A6
F7B0 SubCF7B0
F7BF SubCF7BF
F7C8 SubCF7C8
FFF7 SubCFFF7
# ---- derived internal branch-target names ----
8000 Reset
800A SubC800A_OnNonnegative
8017 SubC8017_OnNonzero
802D SubC802D_Loop
8060 SubC8060_OnNonzero
806F SubC806F
8079 NmiHandler
8081 SubC8081_OnNonnegative
80C1 SubC80C1_OnNonzero
80C8 SubC80C8_OnZero
80CF SubC80CF_Loop
80DD SubC80DD
80E4 SubC80E4_Loop
8106 SubC8106_Loop
810C SubC810C_OnNonnegative
8126 SubC8126_Loop
8130 SubC8130_Loop
8134 SubC8134_Loop
8163 SubC8163
8331 SubC8331
8347 SubC8347_Loop
834D SubC834D
8351 SubC8351
835B SubC835B_OnZero
835C SubC835C
8365 SubC8365
836C SubC836C
837E SubC837E_Loop
838C SubC838C
8391 SubC8391_OnCarrySet
857B SubC857B
8595 SubC8595_Loop
85A0 SubC85A0_Loop
87BA SubC87BA
87D8 SubC87D8_Loop
87DB SubC87DB_Loop
87ED SubC87ED_Loop
87F0 SubC87F0_Loop
87F1 SubC87F1
8805 SubC8805_Loop
8825 SubC8825
8839 SubC8839_Loop
8859 SubC8859
885D SubC885D_OnNonzero
886A SubC886A_Loop
8872 SubC8872_OnNonnegative
8887 SubC8887_OnNonnegative
8893 SubC8893_OnNonnegative
889D SubC889D_Loop
889E SubC889E_Loop
88A5 SubC88A5_Loop
88AD SubC88AD_OnNonnegative
88C2 SubC88C2_OnNonnegative
88CE SubC88CE_OnNonnegative
88D8 SubC88D8_Loop
88D9 SubC88D9
88E3 SubC88E3_Loop
88E6 SubC88E6_OnNonzero
88E7 SubC88E7
88F1 SubC88F1_Loop
88F4 SubC88F4_Loop
88F5 SubC88F5
88FF SubC88FF_Loop
8900 SubC8900
890C SubC890C_Loop
890D SubC890D
8919 SubC8919_Loop
891A SubC891A
891E SubC891E_OnNonzero
892B SubC892B_Loop
8932 SubC8932_Loop
8941 SubC8941_Loop
8959 SubC8959
8960 SubC8960
896E SubC896E_Loop
8979 SubC8979_Loop
898B SubC898B_OnNonzero
8996 SubC8996_Loop
8999 SubC8999_Loop
89A7 SubC89A7_Loop
89B3 SubC89B3_Loop
89BE SubC89BE_Loop
89BF SubC89BF
89C3 SubC89C3_OnNonzero
89D0 SubC89D0_Loop
89D5 SubC89D5_OnNonnegative
89DF SubC89DF_OnNonzero
89ED SubC89ED_Loop
89F4 SubC89F4_Loop
89F9 SubC89F9_OnNonnegative
8A03 SubC8A03_OnNonzero
8A5B SubC8A5B
8A60 SubC8A60_Loop
8A6E SubC8A6E_Loop
8A72 SubC8A72
8A80 SubC8A80_Loop
8A81 SubC8A81
8A8B SubC8A8B_Loop
8A8C SubC8A8C
8A9F SubC8A9F
8D04 SubC8D04
8D12 SubC8D12_OnCarryClear
8D2D SubC8D2D_Loop
8D38 SubC8D38_Loop
8D3E SubC8D3E
8D47 SubC8D47_Loop
8D4D SubC8D4D_Loop
8D4E SubC8D4E
8D6F SubC8D6F_Loop
8D82 SubC8D82_Loop
8D86 SubC8D86_OnNonzero
8D87 SubC8D87
8D91 SubC8D91_Loop
8DAA SubC8DAA_Loop
8DBA SubC8DBA_Loop
8DD3 SubC8DD3_Loop
8DD9 SubC8DD9_Loop
8DE5 SubC8DE5
8DF3 SubC8DF3_Loop
8DF9 SubC8DF9_Loop
8E1D SubC8E1D_Loop
8E20 SubC8E20_Loop
8E21 SubC8E21
8E2E SubC8E2E_Loop
8E45 SubC8E45_Loop
8E55 SubC8E55
8E62 SubC8E62_Loop
8E7F SubC8E7F_Loop
8E8E SubC8E8E_Loop
8E8F SubC8E8F
8E9C SubC8E9C
8EA8 SubC8EA8_Loop
8EB9 SubC8EB9_Loop
8EDF SubC8EDF_Loop
8EE2 SubC8EE2
8EFA SubC8EFA
8FAA SubC8FAA
8FAE SubC8FAE_OnNonnegative
8FD1 SubC8FD1_Loop
8FDD SubC8FDD_Loop
8FE3 SubC8FE3
8FF1 SubC8FF1_Loop
8FF4 SubC8FF4_Loop
9002 SubC9002_OnNonnegative
9031 SubC9031_OnNonnegative
903A SubC903A_Loop
9096 SubC9096
90A8 SubC90A8_OnNonzero
90F6 SubC90F6_Loop
9101 SubC9101_Loop
9108 SubC9108_Loop
911E SubC911E
9128 SubC9128_OnNonnegative
913B SubC913B_Loop
9143 SubC9143
914D SubC914D_OnNonnegative
9160 SubC9160_Loop
916E SubC916E
9170 SubC9170_OnNonnegative
9183 SubC9183_Loop
918B SubC918B
918D SubC918D_OnNonnegative
91A0 SubC91A0_Loop
91A8 SubC91A8
91AC SubC91AC_OnNonnegative
91CF SubC91CF_Loop
91DB SubC91DB_Loop
91E1 SubC91E1
91EF SubC91EF_Loop
91F2 SubC91F2_Loop
91F6 SubC91F6_OnNonnegative
9206 SubC9206_Loop
9216 SubC9216_Loop
9229 SubC9229
922B SubC922B
9235 SubC9235_OnNonnegative
9264 SubC9264_Loop
926C SubC926C_Loop
9288 SubC9288_Loop
92AF SubC92AF_Loop
92B7 SubC92B7_Loop
92BA SubC92BA_Loop
92C4 SubC92C4_OnNonnegative
92F3 SubC92F3_Loop
92F4 SubC92F4_Loop
92FB SubC92FB
930E SubC930E_OnNonnegative
9356 SubC9356_Loop
935D SubC935D_Loop
9369 SubC9369_Loop
936A SubC936A
937F SubC937F_Loop
9391 SubC9391_Loop
93A7 SubC93A7_Loop
93BA SubC93BA
93D1 SubC93D1_Loop
93D9 SubC93D9_Loop
93DD SubC93DD_Loop
93E7 SubC93E7_Loop
93E9 SubC93E9_Loop
93EC SubC93EC_OnZero
93FD SubC93FD
9401 SubC9401_OnNonnegative
9426 SubC9426
9434 SubC9434_Loop
9437 SubC9437_Loop
943B SubC943B_OnNonnegative
9448 SubC9448_Loop
945B SubC945B_Loop
9465 SubC9465_OnZero
9469 SubC9469
9471 SubC9471
947B SubC947B_OnNonnegative
94A1 SubC94A1_Loop
94C8 SubC94C8_Loop
94D3 SubC94D3_Loop
94F3 SubC94F3_Loop
94FD SubC94FD_OnNonnegative
9511 SubC9511_OnNonzero
9512 SubC9512
9523 SubC9523_OnZero
9526 SubC9526_Loop
9537 SubC9537_Loop
9569 SubC9569_Loop
958F SubC958F_Loop
95AD SubC95AD_Loop
95B3 SubC95B3_Loop
95B6 SubC95B6
95CF SubC95CF_Loop
95DF SubC95DF_Loop
95ED SubC95ED_Loop
95F9 SubC95F9_Loop
9604 SubC9604_Loop
9608 SubC9608
962A SubC962A_Loop
9631 SubC9631
964E SubC964E_Loop
965A SubC965A
965C SubC965C_OnNonnegative
966F SubC966F_Loop
9677 SubC9677
9679 SubC9679_OnNonnegative
968C SubC968C_Loop
9694 SubC9694
96A6 SubC96A6_Loop
96A9 SubC96A9_Loop
96AA SubC96AA
96E9 SubC96E9
96F3 SubC96F3_OnNonnegative
96FA SubC96FA_OnNonzero
9700 SubC9700_Loop
9719 SubC9719_Loop
9728 SubC9728_Loop
9744 SubC9744_Loop
9753 SubC9753_Loop
976A SubC976A_Loop
9775 SubC9775_Loop
977C SubC977C_Loop
977D SubC977D
9795 SubC9795_OnCarryClear
9797 SubC9797_OnCarryClear
97A1 SubC97A1_Loop
97AC SubC97AC_Loop
97BC SubC97BC_Loop
97D4 SubC97D4
97E0 SubC97E0_OnNonzero
97EB SubC97EB_Loop
97EE SubC97EE_Loop
97FE SubC97FE_Loop
980F SubC980F
9824 SubC9824_Loop
9842 SubC9842_OnNonnegative
984C SubC984C_Loop
984D SubC984D_Loop
985B SubC985B_Loop
9879 SubC9879_OnNonnegative
9883 SubC9883_Loop
9884 SubC9884
98FD SubC98FD
990F SubC990F_Loop
991D SubC991D_Loop
9930 SubC9930_Loop
993E SubC993E_Loop
995A SubC995A_Loop
9966 SubC9966_Loop
997F SubC997F_Loop
998B SubC998B_Loop
999D SubC999D_Loop
99AF SubC99AF_Loop
99BE SubC99BE_Loop
99C5 SubC99C5_Loop
99C6 SubC99C6
99D2 SubC99D2_Loop
99DB SubC99DB_Loop
99DE SubC99DE_OnCarryClear
99F2 SubC99F2_Loop
9A00 SubC9A00_Loop
9A13 SubC9A13_Loop
9A1F SubC9A1F_Loop
9A36 SubC9A36_Loop
9A5C SubC9A5C
9A65 SubC9A65_Loop
9A6F SubC9A6F_Loop
9A79 SubC9A79_Loop
9A7C SubC9A7C_Loop
9AB3 SubC9AB3_Loop
9AC2 SubC9AC2_OnNonzero
9AEE SubC9AEE_Loop
9AF4 SubC9AF4_Loop
9AFA SubC9AFA_Loop
9B0B SubC9B0B_OnNonzero
9B15 SubC9B15_Loop
A07E SubCA07E
A08F SubCA08F_Loop
A092 SubCA092_Loop
A0A4 SubCA0A4_Loop
A0A5 SubCA0A5_Loop
A0BE SubCA0BE_Loop
A0E0 SubCA0E0_Loop
A0E1 SubCA0E1
A110 SubCA110_Loop
A122 SubCA122_Loop
A12F SubCA12F_Loop
A148 SubCA148_Loop
A149 SubCA149_Loop
A155 SubCA155_Loop
A165 SubCA165
A172 SubCA172_Loop
A18B SubCA18B_Loop
A18E SubCA18E_Loop
A18F SubCA18F
A19C SubCA19C_Loop
A1B6 SubCA1B6_Loop
A1B9 SubCA1B9_Loop
A1BA SubCA1BA
A1D1 SubCA1D1_Loop
A1D4 SubCA1D4_Loop
A1D5 SubCA1D5
A1EC SubCA1EC_Loop
A1EF SubCA1EF_OnZero
A1F0 SubCA1F0
A225 SubCA225_Loop
A234 SubCA234_Loop
A247 SubCA247_Loop
A252 SubCA252
A287 SubCA287_Loop
A296 SubCA296_Loop
A2A9 SubCA2A9_Loop
A2B3 SubCA2B3_Loop
A2B4 SubCA2B4
A2CE SubCA2CE_Loop
A2D9 SubCA2D9
A2FF SubCA2FF
A30B SubCA30B_Loop
A318 SubCA318
A340 SubCA340_Loop
A34E SubCA34E_Loop
A367 SubCA367_Loop
A371 SubCA371_Loop
A372 SubCA372_OnNonnegative
A379 SubCA379_Loop
A37F SubCA37F
A398 SubCA398_Loop
A3A2 SubCA3A2_Loop
A3AC SubCA3AC_Loop
A3BC SubCA3BC_Loop
A3C7 SubCA3C7_Loop
A3D2 SubCA3D2_Loop
A3DF SubCA3DF_Loop
A3EA SubCA3EA_Loop
A3ED SubCA3ED_Loop
A401 SubCA401_OnNonnegative
A409 SubCA409_Loop
A40F SubCA40F
A424 SubCA424_Loop
A439 SubCA439_Loop
A43F SubCA43F_Loop
A443 SubCA443
A45F SubCA45F_Loop
A46A SubCA46A_Loop
A47E SubCA47E
A487 SubCA487_Loop
A488 SubCA488
A48A SubCA48A_OnNonzero
A49D SubCA49D_Loop
A4A5 SubCA4A5
A4A7 SubCA4A7_OnNonzero
A4BA SubCA4BA_Loop
A4C2 SubCA4C2
A4CD SubCA4CD
A4D7 SubCA4D7_OnNonzero
A52E SubCA52E_OnZero
A52F SubCA52F
A53D SubCA53D_OnNonnegative
A581 SubCA581
A596 SubCA596_OnCarryClear
A5A2 SubCA5A2_Loop
A5AE SubCA5AE_Loop
A5B2 SubCA5B2_Loop
A5B5 SubCA5B5_Loop
A5DB SubCA5DB_Loop
A5E0 SubCA5E0_Loop
A5ED SubCA5ED_Loop
A5F2 SubCA5F2_Loop
A5FC SubCA5FC_Loop
A679 SubCA679
A686 SubCA686_OnNonzero
A68E SubCA68E_Loop
A697 SubCA697_Loop
A69A SubCA69A_Loop
A6B2 SubCA6B2_Loop
A6BC SubCA6BC_Loop
A764 SubCA764
A78C SubCA78C_Loop
A78E SubCA78E_Loop
A792 SubCA792_Loop
A793 SubCA793
A7BB SubCA7BB_Loop
A7C9 SubCA7C9_Loop
A7CA SubCA7CA_OnNonnegative
A7D1 SubCA7D1_Loop
A7D7 SubCA7D7
A805 SubCA805_Loop
A807 SubCA807_Loop
A825 SubCA825_Loop
A834 SubCA834_Loop
A83E SubCA83E_Loop
A84E SubCA84E_Loop
A867 SubCA867_Loop
A86E SubCA86E_Loop
A887 SubCA887_Loop
A88E SubCA88E_Loop
A89B SubCA89B_Loop
A8A9 SubCA8A9_Loop
A8AC SubCA8AC_Loop
A8C5 SubCA8C5_OnNonnegative
A8CD SubCA8CD_Loop
A8D3 SubCA8D3
A8DB SubCA8DB_Loop
A8DC SubCA8DC
A8FE SubCA8FE_Loop
A904 SubCA904_Loop
A908 SubCA908
A92F SubCA92F_Loop
A93A SubCA93A_Loop
A940 SubCA940
A94B SubCA94B_Loop
A955 SubCA955_Loop
A958 SubCA958_Loop
A960 SubCA960_Loop
A96F SubCA96F_Loop
A98F SubCA98F_Loop
A9AA SubCA9AA_Loop
A9B7 SubCA9B7_Loop
A9C8 SubCA9C8_Loop
A9CB SubCA9CB_Loop
A9CC SubCA9CC
A9E4 SubCA9E4_Loop
A9FB SubCA9FB_Loop
A9FC SubCA9FC_Loop
AA21 SubCAA21_Loop
AA22 SubCAA22
AA2F SubCAA2F_Loop
AA4A SubCAA4A_Loop
AA4D SubCAA4D_Loop
AA4E SubCAA4E
AA5B SubCAA5B_Loop
AA77 SubCAA77_Loop
AA7A SubCAA7A_Loop
AA7B SubCAA7B
AA91 SubCAA91_Loop
AA94 SubCAA94_Loop
AA95 SubCAA95
AAC0 SubCAAC0_Loop
AAC1 SubCAAC1
AAD7 SubCAAD7_Loop
AADA SubCAADA_OnZero
AADB SubCAADB
AB01 SubCAB01_Loop
AB22 SubCAB22_Loop
AB35 SubCAB35_OnNonnegative
AB3B SubCAB3B_Loop
AB63 SubCAB63_Loop
AB6B SubCAB6B_OnNonzero
AB6F SubCAB6F
AB81 SubCAB81_Loop
AB97 SubCAB97_Loop
AB9A SubCAB9A_Loop
AB9D SubCAB9D_Loop
ABA0 SubCABA0
ABC6 SubCABC6_Loop
ABE8 SubCABE8_Loop
ABF7 SubCABF7_Loop
AC1A SubCAC1A_Loop
AC22 SubCAC22_Loop
AC23 SubCAC23
AC36 SubCAC36_Loop
AC3C SubCAC3C_Loop
AC3F SubCAC3F
AC5E SubCAC5E_Loop
AC71 SubCAC71_OnCarrySet
AC76 SubCAC76_OnNonzero
AC77 SubCAC77
AC96 SubCAC96_Loop
ACB0 SubCACB0
ACBD SubCACBD_Loop
ACC1 SubCACC1
ACCA SubCACCA_Loop
ACEB SubCACEB
ACF7 SubCACF7_Loop
ACFC SubCACFC
AD30 SubCAD30_Loop
AD49 SubCAD49_Loop
AD54 SubCAD54
AD63 SubCAD63_Loop
ADFF SubCADFF
AE01 SubCAE01
AE5F SubCAE5F_Loop
AE7A SubCAE7A_Loop
AE86 SubCAE86_Loop
AE87 SubCAE87
AE9B SubCAE9B_OnNonnegative
AEA7 SubCAEA7_Loop
AF14 SubCAF14
AF18 SubCAF18_OnNonzero
AF22 SubCAF22
AF49 SubCAF49_Loop
AF4A SubCAF4A
AF4C SubCAF4C_OnZero
AF58 SubCAF58_OnNonzero
AF77 SubCAF77_Loop
AF94 SubCAF94
AFB0 SubCAFB0_OnNonzero
AFBF SubCAFBF_OnNonzero
AFC9 SubCAFC9_Loop
AFD7 SubCAFD7_Loop
AFD8 SubCAFD8
AFDF SubCAFDF
AFF4 SubCAFF4_OnNonzero
B00A SubCB00A_OnNonzero
B023 SubCB023_OnNonzero
B02A SubCB02A
B036 SubCB036_OnNonnegative
B03C SubCB03C_Loop
B046 SubCB046_Loop
B04B SubCB04B
B069 SubCB069
B076 SubCB076_Loop
B082 SubCB082_Loop
B08B SubCB08B_Loop
B095 SubCB095
B09F SubCB09F_Loop
B0A7 SubCB0A7_Loop
B0AE SubCB0AE_OnNonzero
B0C4 SubCB0C4_Loop
B0D0 SubCB0D0_Loop
B0D3 SubCB0D3_OnNonzero
B0D6 SubCB0D6_Loop
B0EA SubCB0EA
B0F4 SubCB0F4
B104 SubCB104
B11B SubCB11B_OnNonzero
B132 SubCB132_OnNonzero
B15C SubCB15C
B16C SubCB16C_Loop
B16D SubCB16D
B17C SubCB17C
B187 SubCB187_Loop
B194 SubCB194_OnCarrySet
B198 SubCB198_Loop
B19D SubCB19D
B1B0 SubCB1B0_Loop
B1BC SubCB1BC_Loop
B1BF SubCB1BF
B1DA SubCB1DA
B1F8 SubCB1F8
B203 SubCB203_OnZero
B20A SubCB20A
B220 SubCB220
B230 SubCB230
B239 SubCB239
B244 SubCB244
B24C SubCB24C_OnNonzero
B24E SubCB24E_OnNonzero
B28B SubCB28B
B29B SubCB29B
B29F SubCB29F
B2A3 SubCB2A3
B2A7 SubCB2A7
B2AB SubCB2AB
B2AF SubCB2AF
B2B3 SubCB2B3
B2B7 SubCB2B7
B2B9 SubCB2B9_Loop
B2C2 SubCB2C2
B2C8 SubCB2C8_Loop
B2CF SubCB2CF_Loop
B2D5 SubCB2D5
B2DD SubCB2DD
B2E5 SubCB2E5
B2E9 SubCB2E9
B2F1 SubCB2F1
B2F3 SubCB2F3_Loop
B2FC SubCB2FC
B300 SubCB300
B308 SubCB308
B30C SubCB30C
B310 SubCB310
B314 SubCB314
B316 SubCB316_Loop
B31B SubCB31B
B32F SubCB32F_Loop
B336 SubCB336_Loop
B33C SubCB33C
B345 SubCB345
B346 SubCB346
B347 SubCB347
B34C SubCB34C
B352 SubCB352
B357 SubCB357
B359 SubCB359
F0A0 SubCF0A0
F0A4 SubCF0A4
F0A8 SubCF0A8
F0AC SubCF0AC
F0AE SubCF0AE_Loop
F0BA SubCF0BA_OnNonzero
F0C5 SubCF0C5
F0D2 SubCF0D2_OnNonzero
F112 SubCF112
F11A SubCF11A
F11F SubCF11F_OnZero
F122 SubCF122_OnZero
F123 SubCF123
F12A SubCF12A_OnZero
F12D SubCF12D_OnNonzero
F13A SubCF13A_Loop
F150 SubCF150
F166 SubCF166_Loop
F172 SubCF172_Loop
F17D SubCF17D_Loop
F180 SubCF180
F194 SubCF194
F19A SubCF19A_Loop
F1BF SubCF1BF_Loop
F1D0 SubCF1D0_Loop
F1D2 SubCF1D2_Loop
F1DE SubCF1DE
F1E5 SubCF1E5_Loop
F1ED SubCF1ED_Loop
F1F6 SubCF1F6_Loop
F201 SubCF201_Loop
F209 SubCF209_Loop
F222 SubCF222_Loop
F225 SubCF225
F23A SubCF23A_OnZero
F23B SubCF23B_OnZero
F248 SubCF248
F26B SubCF26B_Loop
F284 SubCF284_Loop
F289 SubCF289_Loop
F29C SubCF29C_Loop
F2A1 SubCF2A1_Loop
F2A6 SubCF2A6_Loop
F2A9 SubCF2A9_Loop
F2B0 SubCF2B0_OnZero
F2C9 SubCF2C9_OnCarrySet
F2DC SubCF2DC_OnCarrySet
F2E2 SubCF2E2
F305 SubCF305
F30F SubCF30F_OnZero
F310 SubCF310_Loop
F32B SubCF32B_Loop
F337 SubCF337
F34F SubCF34F_Loop
F353 SubCF353
F38C SubCF38C_OnCarrySet
F39D SubCF39D_OnCarrySet
F3AA SubCF3AA
F3BE SubCF3BE_Loop
F3CC SubCF3CC
F3D4 SubCF3D4_OnNonzero
F3D5 SubCF3D5_Loop
F3DF SubCF3DF
F43B SubCF43B_OnNonzero
F44F SubCF44F
F457 SubCF457_OnCarrySet
F45F SubCF45F_OnCarrySet
F467 SubCF467_OnCarrySet
F46F SubCF46F_OnCarrySet
F490 SubCF490_OnCarrySet
F4AA SubCF4AA_Loop
F4BD SubCF4BD_OnCarrySet
F4C0 SubCF4C0
F4F9 SubCF4F9_OnNonzero
F4FA SubCF4FA_Loop
F50B SubCF50B_Loop
F518 SubCF518_Loop
F533 SubCF533_Loop
F537 SubCF537
F555 SubCF555_Loop
F561 SubCF561_OnZero
F564 SubCF564_Loop
F575 SubCF575_Loop
F598 SubCF598_OnCarrySet
F5A2 SubCF5A2_OnCarrySet
F5BE SubCF5BE_OnCarrySet
F5CB SubCF5CB
F5E7 SubCF5E7_OnNonzero
F5E8 SubCF5E8
F5FB SubCF5FB_Loop
F61A SubCF61A_Loop
F63B SubCF63B_Loop
F660 SubCF660_OnNonzero
F674 SubCF674_OnNonzero
F690 SubCF690
F6B2 SubCF6B2_Loop
F6CB SubCF6CB
F6D9 SubCF6D9_OnCarrySet
F6E0 SubCF6E0_OnZero
F6E7 SubCF6E7_OnCarrySet
F6F1 SubCF6F1_OnCarrySet
F6F8 SubCF6F8_OnCarrySet
F704 SubCF704
F747 SubCF747_Loop
F74A SubCF74A_Loop
F751 SubCF751_Loop
F758 SubCF758_Loop
F75F SubCF75F_Loop
F76B SubCF76B_Loop
F771 SubCF771_Loop
F77D SubCF77D
F784 SubCF784_OnZero
F794 SubCF794
F79D SubCF79D_Loop
F7A6 SubCF7A6
F7AD SubCF7AD_OnNonzero
F7B0 SubCF7B0
F7B7 SubCF7B7_OnNonzero
F7BF SubCF7BF
F7C8 SubCF7C8
FFF7 SubCFFF7