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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PROMPTS.md gains two Pass 3 requirements:

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

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

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

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

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

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

All seven projects still build byte-identical.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Three lessons from the seven re-splits:

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

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

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

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

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

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

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

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

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

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

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

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

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

derive_routine_docs.py: describe what each routine actually does

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

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

Rewrite the routine headers across the promoted tier

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

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

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

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

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

CHANGELOG: record the tier-wide routine header rewrite

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

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

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

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

make still prints Byte-identical ROM verified.

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

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

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

Two real bugs are fixed on the way:

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

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

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

Complete Pass 2 across the tier: no Label_ residue left

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

Three more real defects in the tools are fixed:

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

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

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

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

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

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

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

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

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

apply_pass2_map.py: do not write the same equate twice

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

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

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

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

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

All 61 promoted projects now carry the section.

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

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

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

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

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

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

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

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

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

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

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

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

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

Repair the damaged audit trails across the tier

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

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

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

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

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

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

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

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

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

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

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

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

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

Give every routine header a contract that is its own

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Interpret the data tables across the tier

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

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: move the committed entries into History

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

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

Root README: refresh the coverage column of the project inventory

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

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

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

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

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

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

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

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

TODO.md: bring the handoff up to date

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

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

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

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

Three gaps it found, now closed:

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

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

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

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

Every project still prints Byte-identical ROM verified.

PROMPTS.md: the checklist now has a checker

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

CHANGELOG: record the checklist work

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the zero-page residue work

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

The promoted tier now passes every item of the promotion checklist

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the tier passing the checklist

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

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

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

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

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

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

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

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

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

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

Remaining entry-point naming

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

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

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

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

CHANGELOG: record the entry-point naming

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

Re-align the audit comments to the canonical column

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

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

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

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

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

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

CHANGELOG: record the audit-comment re-alignment

Remaining entry-point naming

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

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

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

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

CHANGELOG: record the tier reaching completion

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

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

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

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

Every project still prints Byte-identical ROM verified.

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

17 KiB

1C000Reset
2C094NmiHandler
3C0F7IrqHandler
4C0FASubCC0FA
5C104SubCC104
6C10ASubCC10A
7C115SubCC115
8C119SubCC119
9C12DSubCC12D
10C131SubCC131
11C154SubCC154
12C17CSubCC17C
13C1C5SubCC1C5
14C209SubCC209
15C3B2SubCC3B2
16C405SubCC405
17C43ESubCC43E
18C454SubCC454
19C46BSubCC46B
20C486SubCC486
21C527SubCC527
22C539SubCC539
23C579SubCC579
24C5C3SubCC5C3
25C5D8SubCC5D8
26C614SubCC614
27C64BSubCC64B
28C658SubCC658
29C6C4SubCC6C4
30C6F9SubCC6F9
31C716SubCC716
32C726SubCC726
33C77ASubCC77A
34C784SubCC784
35C790SubCC790
36C831SubCC831
37C883SubCC883
38C8B7SubCC8B7
39C8B9SubCC8B9
40C9AFSubCC9AF
41C9B6SubCC9B6
42CA37SubCCA37
43CA3DSubCCA3D
44CA4FSubCCA4F
45CA55SubCCA55
46CA67SubCCA67
47CA69SubCCA69
48CAE1SubCCAE1
49CB1CSubCCB1C
50CB74SubCCB74
51CBA8SubCCBA8
52CC33SubCCC33
53CC3ASubCCC3A
54CCBFSubCCCBF
55CCCBSubCCCCB
56CD0FSubCCD0F
57CD4ASubCCD4A
58CD5ASubCCD5A
59CDAASubCCDAA
60CDACSubCCDAC
61CE2FSubCCE2F
62CECESubCCECE
63CF13SubCCF13
64D0E2SubCD0E2
65D121SubCD121
66D1A0SubCD1A0
67D1C9SubCD1C9
68D1CBSubCD1CB
69D1DCSubCD1DC
70D213SubCD213
71D246SubCD246
72D275SubCD275
73D293SubCD293
74D2B1SubCD2B1
75D327SubCD327
76D3BASubCD3BA
77D3E1SubCD3E1
78D3EDSubCD3ED
79D468SubCD468
80D48CSubCD48C
81D4E5SubCD4E5
82D4F0SubCD4F0
83D4FBSubCD4FB
84D51CSubCD51C
85D53CSubCD53C
86D56CSubCD56C
87D572SubCD572
88D593SubCD593
89D5B8SubCD5B8
90D5C9SubCD5C9
91D5D9SubCD5D9
92D5F1SubCD5F1
93D60DSubCD60D
94D651SubCD651
95D6DCSubCD6DC
96D6DESubCD6DE
97D77CSubCD77C
98D78FSubCD78F
99D798SubCD798
100D826SubCD826
101D871SubCD871
102D8DDSubCD8DD
103D8FFSubCD8FF
104D90FSubCD90F
105DACBSubCDACB
106DB08SubCDB08
107E3A4SubCE3A4
108E4D5SubCE4D5
109E587SubCE587
110E691SubCE691
111E6E9SubCE6E9
112E768SubCE768
113E76ASubCE76A
114E796SubCE796
115E7B1SubCE7B1
116E901SubCE901
117E93ESubCE93E
118E983SubCE983
119EA18SubCEA18
120EA58SubCEA58
121EB8ESubCEB8E
122EBA0SubCEBA0
123EBB2SubCEBB2
124EBBBSubCEBBB
125EBC4SubCEBC4
126ECBASubCECBA
127ED28SubCED28
128ED44SubCED44
129EDE1SubCEDE1
130EE25SubCEE25
131EE27SubCEE27
132EF2ASubCEF2A
133EF37SubCEF37
134F08ESubCF08E
135F098SubCF098
136F0A6SubCF0A6
137F0B4SubCF0B4
138F0BDSubCF0BD
139F0DESubCF0DE
140F107SubCF107
141F119SubCF119
142F172SubCF172
143F18CSubCF18C
144F1A6SubCF1A6
145F1B3SubCF1B3
146F1D4SubCF1D4
147F1F2SubCF1F2
148F213SubCF213
149F353SubCF353
150F36ASubCF36A
151F386SubCF386
152F3B0SubCF3B0
153F3CCSubCF3CC
154F40BSubCF40B
155F45CSubCF45C
156F465SubCF465
157F470SubCF470
158F4A5SubCF4A5
159F504SubCF504
160F531SubCF531
161F561SubCF561
162F575SubCF575
163F5B2SubCF5B2
164F683SubCF683
165F687SubCF687
166F68BSubCF68B
167F68FSubCF68F
168F6A8SubCF6A8
169F712SubCF712
170F71ASubCF71A
171F725SubCF725
172F758SubCF758
173F77CSubCF77C
174F78FSubCF78F
175F798SubCF798
176F824SubCF824
177F879SubCF879
178F89BSubCF89B
179F8A6SubCF8A6
180F8BFSubCF8BF
181F8CASubCF8CA
182F90ASubCF90A
183F9BDSubCF9BD
184FA38SubCFA38
185FAACSubCFAAC
186FB25SubCFB25
187FFF7SubCFFF7
188# ---- derived internal branch-target names ----
189C000Reset
190C008SubCC008_OnNonnegative
191C00DSubCC00D_OnNegative
192C012SubCC012_OnNonnegative
193C020SubCC020_OnNonzero
194C027SubCC027_OnNonnegative
195C034SubCC034_Loop
196C037SubCC037_OnNonzero
197C043SubCC043_OnNonzero
198C055SubCC055_OnNonnegative
199C060SubCC060_OnNonnegative
200C06ESubCC06E_OnNonnegative
201C077SubCC077_Loop
202C094NmiHandler
203C0ACSubCC0AC_Loop
204C0D1SubCC0D1_OnNegative
205C0DASubCC0DA_OnNonzero
206C0F1SubCC0F1_Loop
207C0F7IrqHandler
208C0FASubCC0FA
209C0FESubCC0FE_OnNonzero
210C104SubCC104
211C10ASubCC10A
212C10CSubCC10C_OnNonzero
213C115SubCC115
214C119SubCC119
215C11ESubCC11E_OnNonzero
216C12DSubCC12D
217C131SubCC131
218C144SubCC144_OnNonzero
219C154SubCC154
220C17CSubCC17C
221C188SubCC188_OnNonzero
222C19ESubCC19E_OnNonzero
223C1BESubCC1BE_Loop
224C1C5SubCC1C5
225C1FCSubCC1FC_OnNonnegative
226C209SubCC209
227C216SubCC216_Loop
228C21ESubCC21E_Loop
229C227SubCC227_Loop
230C231SubCC231_Loop
231C247SubCC247_Loop
232C24DSubCC24D_Loop
233C24FSubCC24F_OnNonnegative
234C26DSubCC26D_Loop
235C272SubCC272_OnNonnegative
236C289SubCC289_Loop
237C2BCSubCC2BC_Loop
238C2D0SubCC2D0_Loop
239C2D2SubCC2D2_OnNonnegative
240C2EFSubCC2EF_Loop
241C2F7SubCC2F7_OnNonnegative
242C30DSubCC30D_Loop
243C314SubCC314_Loop
244C317SubCC317_Loop
245C32DSubCC32D_Loop
246C36FSubCC36F_Loop
247C378SubCC378_Loop
248C3A1SubCC3A1_Loop
249C3B2SubCC3B2
250C3F7SubCC3F7_OnNonzero
251C405SubCC405
252C40CSubCC40C_Loop
253C439SubCC439_Loop
254C43ESubCC43E
255C454SubCC454
256C46BSubCC46B
257C46DSubCC46D_OnNonnegative
258C476SubCC476_Loop
259C486SubCC486
260C488SubCC488_OnNonnegative
261C491SubCC491_Loop
262C527SubCC527
263C539SubCC539
264C53DSubCC53D_OnNonzero
265C54BSubCC54B_OnNonnegative
266C559SubCC559_Loop
267C563SubCC563_Loop
268C579SubCC579
269C5A1SubCC5A1_OnNonzero
270C5ACSubCC5AC_Loop
271C5AESubCC5AE_OnNonnegative
272C5C3SubCC5C3
273C5D5SubCC5D5_Loop
274C5D8SubCC5D8
275C5F4SubCC5F4_Loop
276C602SubCC602_Loop
277C607SubCC607_Loop
278C610SubCC610_Loop
279C613SubCC613_Loop
280C614SubCC614
281C61BSubCC61B_OnNonnegative
282C62BSubCC62B_Loop
283C62FSubCC62F_Loop
284C64BSubCC64B
285C657SubCC657_Loop
286C658SubCC658
287C66FSubCC66F_Loop
288C671SubCC671_Loop
289C6A3SubCC6A3_Loop
290C6B3SubCC6B3_Loop
291C6B7SubCC6B7_Loop
292C6C4SubCC6C4
293C6E0SubCC6E0_Loop
294C6EESubCC6EE_Loop
295C6F8SubCC6F8_Loop
296C6F9SubCC6F9
297C709SubCC709_Loop
298C70DSubCC70D_Loop
299C716SubCC716
300C718SubCC718_OnNonnegative
301C726SubCC726
302C72ESubCC72E_Loop
303C77ASubCC77A
304C77ESubCC77E_OnZero
305C781SubCC781_Loop
306C784SubCC784
307C790SubCC790
308C796SubCC796_OnNonzero
309C797SubCC797_Loop
310C7ADSubCC7AD_Loop
311C7B4SubCC7B4_Loop
312C811SubCC811_Loop
313C819SubCC819_Loop
314C821SubCC821_Loop
315C831SubCC831
316C846SubCC846_Loop
317C856SubCC856_Loop
318C883SubCC883
319C88ASubCC88A_Loop
320C8B7SubCC8B7
321C8B9SubCC8B9
322C8C1SubCC8C1_Loop
323C8FFSubCC8FF_Loop
324C937SubCC937_Loop
325C941SubCC941_Loop
326C94ESubCC94E_Loop
327C958SubCC958_Loop
328C962SubCC962_Loop
329C976SubCC976_Loop
330C9ACSubCC9AC_Loop
331C9AFSubCC9AF
332C9B5SubCC9B5_Loop
333C9B6SubCC9B6
334CA37SubCCA37
335CA3DSubCCA3D
336CA4FSubCCA4F
337CA55SubCCA55
338CA67SubCCA67
339CA69SubCCA69
340CA82SubCCA82_Loop
341CA92SubCCA92_Loop
342CAA2SubCCAA2_Loop
343CAA9SubCCAA9_Loop
344CAADSubCCAAD_Loop
345CAC8SubCCAC8_Loop
346CADBSubCCADB_Loop
347CADDSubCCADD_Loop
348CAE1SubCCAE1
349CAE7SubCCAE7_Loop
350CAE8SubCCAE8_Loop
351CAF4SubCCAF4_Loop
352CB00SubCCB00_Loop
353CB0CSubCCB0C_Loop
354CB18SubCCB18_Loop
355CB1CSubCCB1C
356CB1ESubCCB1E_OnNonnegative
357CB70SubCCB70_Loop
358CB74SubCCB74
359CB79SubCCB79_OnNonnegative
360CBA4SubCCBA4_Loop
361CBA7SubCCBA7_Loop
362CBA8SubCCBA8
363CBB2SubCCBB2_OnNonnegative
364CBC1SubCCBC1_Loop
365CBFCSubCCBFC_Loop
366CC0BSubCCC0B_Loop
367CC20SubCCC20_Loop
368CC2FSubCCC2F_Loop
369CC33SubCCC33
370CC3ASubCCC3A
371CC73SubCCC73_Loop
372CCA2SubCCCA2_Loop
373CCB8SubCCCB8_Loop
374CCBESubCCCBE_Loop
375CCBFSubCCCBF
376CCCBSubCCCCB
377CD0FSubCCD0F
378CD25SubCCD25_Loop
379CD4ASubCCD4A
380CD4CSubCCD4C_OnNonnegative
381CD5ASubCCD5A
382CD60SubCCD60_Loop
383CD6BSubCCD6B_OnNonnegative
384CD74SubCCD74_Loop
385CDA2SubCCDA2_Loop
386CDAASubCCDAA
387CDACSubCCDAC
388CDFCSubCCDFC_Loop
389CE0BSubCCE0B_Loop
390CE1DSubCCE1D_Loop
391CE22SubCCE22_Loop
392CE2ESubCCE2E_Loop
393CE2FSubCCE2F
394CE99SubCCE99_Loop
395CECESubCCECE
396CED0SubCCED0_OnNonnegative
397CF0FSubCCF0F_Loop
398CF12SubCCF12_Loop
399CF13SubCCF13
400CF1FSubCCF1F_OnNonnegative
401CF26SubCCF26_Loop
402CF34SubCCF34_OnNonzero
403CF47SubCCF47_Loop
404CF51SubCCF51_OnNonnegative
405CF7ESubCCF7E_OnNonnegative
406CFB5SubCCFB5_OnNonnegative
407CFE8SubCCFE8_Loop
408D013SubCD013_Loop
409D01DSubCD01D_OnNonnegative
410D02ESubCD02E_OnNonnegative
411D04FSubCD04F_OnNonnegative
412D068SubCD068_Loop
413D070SubCD070_OnNonzero
414D08ESubCD08E_Loop
415D0A8SubCD0A8_Loop
416D0C0SubCD0C0_OnNonnegative
417D0CESubCD0CE_Loop
418D0D6SubCD0D6_OnNonnegative
419D0DCSubCD0DC_Loop
420D0E2SubCD0E2
421D104SubCD104_Loop
422D121SubCD121
423D1A0SubCD1A0
424D1A2SubCD1A2_OnNonnegative
425D1C2SubCD1C2_Loop
426D1C9SubCD1C9
427D1CBSubCD1CB
428D1D5SubCD1D5_Loop
429D1DCSubCD1DC
430D1EDSubCD1ED_Loop
431D1FBSubCD1FB_Loop
432D1FESubCD1FE_Loop
433D200SubCD200_OnNonzero
434D208SubCD208_Loop
435D212SubCD212_Loop
436D213SubCD213
437D232SubCD232_Loop
438D238SubCD238_Loop
439D243SubCD243_Loop
440D246SubCD246
441D268SubCD268_OnNonnegative
442D275SubCD275
443D279SubCD279_OnNonzero
444D28CSubCD28C_OnNonzero
445D293SubCD293
446D2A0SubCD2A0_Loop
447D2B1SubCD2B1
448D2C1SubCD2C1_OnNonnegative
449D2CBSubCD2CB_OnNonzero
450D322SubCD322_Loop
451D327SubCD327
452D37ESubCD37E_Loop
453D399SubCD399_Loop
454D39ASubCD39A_OnNonnegative
455D3BASubCD3BA
456D3E1SubCD3E1
457D3EDSubCD3ED
458D3EFSubCD3EF_OnNonnegative
459D404SubCD404_OnNonnegative
460D40DSubCD40D_OnNonzero
461D410SubCD410_Loop
462D421SubCD421_OnNonnegative
463D42DSubCD42D_OnNonnegative
464D468SubCD468
465D48CSubCD48C
466D492SubCD492_Loop
467D497SubCD497_OnZero
468D4A4SubCD4A4_OnZero
469D4CCSubCD4CC_OnNonzero
470D4D8SubCD4D8_Loop
471D4DBSubCD4DB_OnNonzero
472D4E4SubCD4E4_Loop
473D4E5SubCD4E5
474D4EFSubCD4EF_Loop
475D4F0SubCD4F0
476D4FASubCD4FA_Loop
477D4FBSubCD4FB
478D51CSubCD51C
479D53CSubCD53C
480D56CSubCD56C
481D572SubCD572
482D593SubCD593
483D59BSubCD59B_OnNonzero
484D5B1SubCD5B1_OnNonzero
485D5B8SubCD5B8
486D5C9SubCD5C9
487D5CBSubCD5CB_OnNonzero
488D5D9SubCD5D9
489D5DBSubCD5DB_OnNonzero
490D5F1SubCD5F1
491D60CSubCD60C_Loop
492D60DSubCD60D
493D632SubCD632_OnNonnegative
494D63ASubCD63A_Loop
495D63BSubCD63B_Loop
496D651SubCD651
497D6DCSubCD6DC
498D6DESubCD6DE
499D6E4SubCD6E4_OnNegative
500D6E5SubCD6E5_Loop
501D746SubCD746_OnNonnegative
502D752SubCD752_Loop
503D75BSubCD75B_OnNonzero
504D765SubCD765_Loop
505D767SubCD767_OnNonnegative
506D778SubCD778_Loop
507D77CSubCD77C
508D782SubCD782_OnCarrySet
509D78FSubCD78F
510D794SubCD794_Loop
511D798SubCD798
512D7A0SubCD7A0_Loop
513D7B1SubCD7B1_OnNonnegative
514D7D1SubCD7D1_OnNonnegative
515D7F5SubCD7F5_OnNonnegative
516D802SubCD802_Loop
517D805SubCD805_Loop
518D826SubCD826
519D828SubCD828_OnZero
520D82CSubCD82C_OnNonnegative
521D834SubCD834_Loop
522D83ASubCD83A_Loop
523D83BSubCD83B_Loop
524D841SubCD841_OnNonnegative
525D854SubCD854_Loop
526D856SubCD856_OnNonnegative
527D871SubCD871
528D879SubCD879_OnNonnegative
529D88CSubCD88C_Loop
530D8DDSubCD8DD
531D8DFSubCD8DF_OnNonnegative
532D8FBSubCD8FB_Loop
533D8FFSubCD8FF
534D901SubCD901_OnNonnegative
535D90FSubCD90F
536DAC1SubCDAC1_OnZero
537DACBSubCDACB
538DAEDSubCDAED_Loop
539DAF0SubCDAF0_Loop
540DAF1SubCDAF1_Loop
541DB08SubCDB08
542E3A4SubCE3A4
543E3B3SubCE3B3_Loop
544E3C2SubCE3C2_OnNegative
545E3C4SubCE3C4_OnNonnegative
546E3CFSubCE3CF_Loop
547E408SubCE408_Loop
548E41BSubCE41B_Loop
549E429SubCE429_Loop
550E43CSubCE43C_Loop
551E444SubCE444_Loop
552E44BSubCE44B_Loop
553E459SubCE459_Loop
554E463SubCE463_Loop
555E465SubCE465_Loop
556E47CSubCE47C_Loop
557E486SubCE486_Loop
558E494SubCE494_Loop
559E49ASubCE49A_OnNonnegative
560E4B1SubCE4B1_Loop
561E4CASubCE4CA_Loop
562E4D5SubCE4D5
563E50DSubCE50D_Loop
564E54ASubCE54A_Loop
565E550SubCE550_Loop
566E553SubCE553_Loop
567E584SubCE584_Loop
568E587SubCE587
569E599SubCE599_OnNonzero
570E5A7SubCE5A7_Loop
571E5ADSubCE5AD_OnNonnegative
572E5C4SubCE5C4_Loop
573E691SubCE691
574E696SubCE696_OnNonnegative
575E6A4SubCE6A4_Loop
576E6B8SubCE6B8_Loop
577E6CESubCE6CE_Loop
578E6D9SubCE6D9_Loop
579E6E2SubCE6E2_Loop
580E6E9SubCE6E9
581E6F8SubCE6F8_Loop
582E704SubCE704_OnNonzero
583E705SubCE705_Loop
584E712SubCE712_Loop
585E749SubCE749_Loop
586E74DSubCE74D_Loop
587E75BSubCE75B_Loop
588E768SubCE768
589E76ASubCE76A
590E776SubCE776_OnNonnegative
591E796SubCE796
592E79ASubCE79A_OnCarrySet
593E7A3SubCE7A3_Loop
594E7B1SubCE7B1
595E7E8SubCE7E8_Loop
596E7EFSubCE7EF_Loop
597E802SubCE802_Loop
598E80DSubCE80D_Loop
599E811SubCE811_Loop
600E821SubCE821_Loop
601E829SubCE829_Loop
602E82ESubCE82E_Loop
603E832SubCE832_Loop
604E845SubCE845_Loop
605E850SubCE850_Loop
606E854SubCE854_Loop
607E864SubCE864_Loop
608E874SubCE874_Loop
609E87CSubCE87C_Loop
610E87FSubCE87F_Loop
611E8A6SubCE8A6_Loop
612E8B8SubCE8B8_Loop
613E8C7SubCE8C7_Loop
614E8D1SubCE8D1_Loop
615E8ECSubCE8EC_Loop
616E901SubCE901
617E907SubCE907_Loop
618E929SubCE929_Loop
619E93ESubCE93E
620E951SubCE951_Loop
621E963SubCE963_Loop
622E968SubCE968_Loop
623E976SubCE976_Loop
624E982SubCE982_Loop
625E983SubCE983
626E99ASubCE99A_Loop
627E9A4SubCE9A4_Loop
628E9B6SubCE9B6_Loop
629E9F2SubCE9F2_Loop
630E9F3SubCE9F3_Loop
631E9FDSubCE9FD_Loop
632EA13SubCEA13_Loop
633EA15SubCEA15_Loop
634EA17SubCEA17_Loop
635EA18SubCEA18
636EA2CSubCEA2C_Loop
637EA3ESubCEA3E_Loop
638EA44SubCEA44_Loop
639EA47SubCEA47_Loop
640EA57SubCEA57_Loop
641EA58SubCEA58
642EA60SubCEA60_Loop
643EA8BSubCEA8B_Loop
644EA8CSubCEA8C_Loop
645EA9ESubCEA9E_Loop
646EAB2SubCEAB2_Loop
647EAC1SubCEAC1_Loop
648EAD0SubCEAD0_Loop
649EADCSubCEADC_Loop
650EB05SubCEB05_Loop
651EB0DSubCEB0D_Loop
652EB21SubCEB21_Loop
653EB30SubCEB30_Loop
654EB3FSubCEB3F_Loop
655EB4BSubCEB4B_Loop
656EB5ASubCEB5A_Loop
657EB60SubCEB60_Loop
658EB62SubCEB62_Loop
659EB84SubCEB84_Loop
660EB8DSubCEB8D_Loop
661EB8ESubCEB8E
662EBA0SubCEBA0
663EBB2SubCEBB2
664EBBBSubCEBBB
665EBC4SubCEBC4
666EBD6SubCEBD6_Loop
667EBE3SubCEBE3_Loop
668EBF7SubCEBF7_Loop
669EBFDSubCEBFD_OnCarryClear
670EBFESubCEBFE_Loop
671EC2FSubCEC2F_Loop
672EC37SubCEC37_Loop
673EC38SubCEC38_Loop
674EC49SubCEC49_Loop
675EC5CSubCEC5C_Loop
676EC61SubCEC61_Loop
677EC75SubCEC75_Loop
678EC7ESubCEC7E_Loop
679EC93SubCEC93_Loop
680ECADSubCECAD_Loop
681ECBASubCECBA
682ECDBSubCECDB_Loop
683ECDFSubCECDF_OnNonnegative
684ED22SubCED22_Loop
685ED27SubCED27_OnNegative
686ED28SubCED28
687ED2DSubCED2D_OnNonnegative
688ED2ESubCED2E_Loop
689ED40SubCED40_Loop
690ED44SubCED44
691ED5BSubCED5B_Loop
692ED69SubCED69_Loop
693ED78SubCED78_Loop
694ED85SubCED85_Loop
695ED89SubCED89_Loop
696EDA0SubCEDA0_Loop
697EDB4SubCEDB4_Loop
698EDB6SubCEDB6_Loop
699EDC0SubCEDC0_Loop
700EDC1SubCEDC1_Loop
701EDD6SubCEDD6_Loop
702EDE1SubCEDE1
703EDF0SubCEDF0_Loop
704EDF4SubCEDF4_Loop
705EDFFSubCEDFF_Loop
706EE08SubCEE08_Loop
707EE24SubCEE24_Loop
708EE25SubCEE25
709EE27SubCEE27
710EE2ESubCEE2E_OnZero
711EE31SubCEE31_Loop
712EE6ASubCEE6A_Loop
713EE7CSubCEE7C_Loop
714EE8FSubCEE8F_Loop
715EEAASubCEEAA_Loop
716EEBCSubCEEBC_Loop
717EEC0SubCEEC0_Loop
718EECDSubCEECD_Loop
719EED6SubCEED6_Loop
720EEEDSubCEEED_Loop
721EEF1SubCEEF1_Loop
722EEFASubCEEFA_Loop
723EF03SubCEF03_Loop
724EF1ASubCEF1A_Loop
725EF1ESubCEF1E_Loop
726EF2ASubCEF2A
727EF30SubCEF30_Loop
728EF36SubCEF36_Loop
729EF37SubCEF37
730EF42SubCEF42_Loop
731EF4FSubCEF4F_Loop
732EF56SubCEF56_Loop
733EF61SubCEF61_Loop
734EF72SubCEF72_Loop
735EF7FSubCEF7F_Loop
736EF97SubCEF97_Loop
737EFB7SubCEFB7_Loop
738EFC0SubCEFC0_Loop
739EFCESubCEFCE_Loop
740EFE0SubCEFE0_Loop
741EFE2SubCEFE2_Loop
742EFEASubCEFEA_Loop
743F011SubCF011_Loop
744F023SubCF023_Loop
745F043SubCF043_Loop
746F052SubCF052_Loop
747F08ESubCF08E
748F097SubCF097_Loop
749F098SubCF098
750F0A6SubCF0A6
751F0B4SubCF0B4
752F0BDSubCF0BD
753F0DDSubCF0DD_Loop
754F0DESubCF0DE
755F107SubCF107
756F119SubCF119
757F143SubCF143_Loop
758F14FSubCF14F_OnNonzero
759F16CSubCF16C_Loop
760F172SubCF172
761F18CSubCF18C
762F1A6SubCF1A6
763F1A8SubCF1A8_OnNonzero
764F1B3SubCF1B3
765F1B7SubCF1B7_OnNonzero
766F1D4SubCF1D4
767F1D9SubCF1D9_OnNonnegative
768F1F2SubCF1F2
769F1FASubCF1FA_Loop
770F20DSubCF20D_OnNonnegative
771F213SubCF213
772F221SubCF221_Loop
773F238SubCF238_Loop
774F23ASubCF23A_OnNonnegative
775F26FSubCF26F_OnNonnegative
776F278SubCF278_OnNonnegative
777F28ESubCF28E_Loop
778F29BSubCF29B_Loop
779F2A2SubCF2A2_Loop
780F2B3SubCF2B3_Loop
781F2B9SubCF2B9_OnNonnegative
782F2C5SubCF2C5_Loop
783F2E4SubCF2E4_OnNonnegative
784F30DSubCF30D_Loop
785F318SubCF318_Loop
786F326SubCF326_Loop
787F327SubCF327_Loop
788F329SubCF329_OnNonnegative
789F32FSubCF32F_Loop
790F338SubCF338_OnNonnegative
791F34CSubCF34C_Loop
792F353SubCF353
793F361SubCF361_Loop
794F366SubCF366_Loop
795F36ASubCF36A
796F375SubCF375_OnNonzero
797F383SubCF383_Loop
798F386SubCF386
799F3A1SubCF3A1_Loop
800F3ADSubCF3AD_Loop
801F3B0SubCF3B0
802F3CCSubCF3CC
803F3D4SubCF3D4_OnNonnegative
804F3EESubCF3EE_Loop
805F40BSubCF40B
806F410SubCF410_OnNonnegative
807F41ESubCF41E_OnNonnegative
808F42FSubCF42F_OnNonnegative
809F45CSubCF45C
810F45ESubCF45E_OnNonzero
811F465SubCF465
812F469SubCF469_OnZero
813F46FSubCF46F_OnZero
814F470SubCF470
815F489SubCF489_OnZero
816F4A2SubCF4A2_Loop
817F4A5SubCF4A5
818F500SubCF500_OnZero
819F503SubCF503_OnZero
820F504SubCF504
821F50BSubCF50B_OnZero
822F50ESubCF50E_OnNonzero
823F51BSubCF51B_Loop
824F531SubCF531
825F547SubCF547_Loop
826F553SubCF553_Loop
827F55ESubCF55E_Loop
828F561SubCF561
829F575SubCF575
830F57BSubCF57B_Loop
831F587SubCF587_OnZero
832F599SubCF599_Loop
833F5AASubCF5AA_Loop
834F5ACSubCF5AC_Loop
835F5B2SubCF5B2
836F5B9SubCF5B9_Loop
837F5C4SubCF5C4_Loop
838F5CESubCF5CE_Loop
839F5D9SubCF5D9_Loop
840F5E1SubCF5E1_Loop
841F5F9SubCF5F9_Loop
842F683SubCF683
843F687SubCF687
844F68BSubCF68B
845F68FSubCF68F
846F691SubCF691_Loop
847F69DSubCF69D_OnNonzero
848F6A8SubCF6A8
849F6BESubCF6BE_Loop
850F6C4SubCF6C4_OnNonzero
851F712SubCF712
852F71ASubCF71A
853F71FSubCF71F_OnNonzero
854F725SubCF725
855F736SubCF736_Loop
856F745SubCF745_Loop
857F749SubCF749_Loop
858F758SubCF758
859F77BSubCF77B_OnNonzero
860F77CSubCF77C
861F78FSubCF78F
862F798SubCF798
863F79FSubCF79F_Loop
864F7A5SubCF7A5_Loop
865F7B4SubCF7B4_OnZero
866F7C7SubCF7C7_Loop
867F7D3SubCF7D3_OnZero
868F7D9SubCF7D9_OnZero
869F7E0SubCF7E0_OnZero
870F7EFSubCF7EF_OnZero
871F800SubCF800_OnCarrySet
872F814SubCF814_OnCarrySet
873F821SubCF821_OnCarrySet
874F824SubCF824
875F83BSubCF83B_Loop
876F85BSubCF85B_Loop
877F85CSubCF85C_Loop
878F85FSubCF85F_Loop
879F879SubCF879
880F87DSubCF87D_Loop
881F89BSubCF89B
882F8A1SubCF8A1_Loop
883F8A2SubCF8A2_Loop
884F8A6SubCF8A6
885F8BFSubCF8BF
886F8CASubCF8CA
887F8DDSubCF8DD_OnCarrySet
888F8E8SubCF8E8_Loop
889F907SubCF907_OnCarrySet
890F90ASubCF90A
891F91BSubCF91B_Loop
892F94BSubCF94B_Loop
893F94ESubCF94E_Loop
894F94FSubCF94F_Loop
895F952SubCF952_Loop
896F965SubCF965_Loop
897F977SubCF977_Loop
898F98FSubCF98F_Loop
899F993SubCF993_Loop
900F9B1SubCF9B1_Loop
901F9BDSubCF9BD
902F9CASubCF9CA_Loop
903F9E9SubCF9E9_OnCarrySet
904F9F9SubCF9F9_Loop
905FA0CSubCFA0C_OnCarrySet
906FA26SubCFA26_Loop
907FA27SubCFA27_OnCarrySet
908FA38SubCFA38
909FA42SubCFA42_Loop
910FA63SubCFA63_Loop
911FA64SubCFA64_Loop
912FA7FSubCFA7F_Loop
913FA83SubCFA83_Loop
914FA96SubCFA96_OnCarrySet
915FAACSubCFAAC
916FABASubCFABA_Loop
917FAD8SubCFAD8_Loop
918FAD9SubCFAD9_Loop
919FAE2SubCFAE2_Loop
920FB00SubCFB00_Loop
921FB04SubCFB04_Loop
922FB10SubCFB10_Loop
923FB17SubCFB17_Loop
924FB1ESubCFB1E_OnCarrySet
925FB25SubCFB25
926FB49SubCFB49_OnNonzero
927FB4CSubCFB4C_Loop
928FB52SubCFB52_Loop
929FB58SubCFB58_Loop
930FB5ESubCFB5E_Loop
931FB69SubCFB69_Loop
932FB6DSubCFB6D_Loop
933FB7CSubCFB7C_Loop
934FB82SubCFB82_Loop
935FB86SubCFB86_Loop
936FB8DSubCFB8D_OnNonzero
937FBA5SubCFBA5_Loop
938FBACSubCFBAC_Loop
939FBAFSubCFBAF_Loop
940FBC1SubCFBC1_Loop
941FFF7SubCFFF7