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

943 lines
17 KiB
Plaintext

C000 Reset
C094 NmiHandler
C0F7 IrqHandler
C0FA SubCC0FA
C104 SubCC104
C10A SubCC10A
C115 SubCC115
C119 SubCC119
C12D SubCC12D
C131 SubCC131
C154 SubCC154
C17C SubCC17C
C1C5 SubCC1C5
C209 SubCC209
C3B2 SubCC3B2
C405 SubCC405
C43E SubCC43E
C454 SubCC454
C46B SubCC46B
C486 SubCC486
C527 SubCC527
C539 SubCC539
C579 SubCC579
C5C3 SubCC5C3
C5D8 SubCC5D8
C614 SubCC614
C64B SubCC64B
C658 SubCC658
C6C4 SubCC6C4
C6F9 SubCC6F9
C716 SubCC716
C726 SubCC726
C77A SubCC77A
C784 SubCC784
C790 SubCC790
C831 SubCC831
C883 SubCC883
C8B7 SubCC8B7
C8B9 SubCC8B9
C9AF SubCC9AF
C9B6 SubCC9B6
CA37 SubCCA37
CA3D SubCCA3D
CA4F SubCCA4F
CA55 SubCCA55
CA67 SubCCA67
CA69 SubCCA69
CAE1 SubCCAE1
CB1C SubCCB1C
CB74 SubCCB74
CBA8 SubCCBA8
CC33 SubCCC33
CC3A SubCCC3A
CCBF SubCCCBF
CCCB SubCCCCB
CD0F SubCCD0F
CD4A SubCCD4A
CD5A SubCCD5A
CDAA SubCCDAA
CDAC SubCCDAC
CE2F SubCCE2F
CECE SubCCECE
CF13 SubCCF13
D0E2 SubCD0E2
D121 SubCD121
D1A0 SubCD1A0
D1C9 SubCD1C9
D1CB SubCD1CB
D1DC SubCD1DC
D213 SubCD213
D246 SubCD246
D275 SubCD275
D293 SubCD293
D2B1 SubCD2B1
D327 SubCD327
D3BA SubCD3BA
D3E1 SubCD3E1
D3ED SubCD3ED
D468 SubCD468
D48C SubCD48C
D4E5 SubCD4E5
D4F0 SubCD4F0
D4FB SubCD4FB
D51C SubCD51C
D53C SubCD53C
D56C SubCD56C
D572 SubCD572
D593 SubCD593
D5B8 SubCD5B8
D5C9 SubCD5C9
D5D9 SubCD5D9
D5F1 SubCD5F1
D60D SubCD60D
D651 SubCD651
D6DC SubCD6DC
D6DE SubCD6DE
D77C SubCD77C
D78F SubCD78F
D798 SubCD798
D826 SubCD826
D871 SubCD871
D8DD SubCD8DD
D8FF SubCD8FF
D90F SubCD90F
DACB SubCDACB
DB08 SubCDB08
E3A4 SubCE3A4
E4D5 SubCE4D5
E587 SubCE587
E691 SubCE691
E6E9 SubCE6E9
E768 SubCE768
E76A SubCE76A
E796 SubCE796
E7B1 SubCE7B1
E901 SubCE901
E93E SubCE93E
E983 SubCE983
EA18 SubCEA18
EA58 SubCEA58
EB8E SubCEB8E
EBA0 SubCEBA0
EBB2 SubCEBB2
EBBB SubCEBBB
EBC4 SubCEBC4
ECBA SubCECBA
ED28 SubCED28
ED44 SubCED44
EDE1 SubCEDE1
EE25 SubCEE25
EE27 SubCEE27
EF2A SubCEF2A
EF37 SubCEF37
F08E SubCF08E
F098 SubCF098
F0A6 SubCF0A6
F0B4 SubCF0B4
F0BD SubCF0BD
F0DE SubCF0DE
F107 SubCF107
F119 SubCF119
F172 SubCF172
F18C SubCF18C
F1A6 SubCF1A6
F1B3 SubCF1B3
F1D4 SubCF1D4
F1F2 SubCF1F2
F213 SubCF213
F353 SubCF353
F36A SubCF36A
F386 SubCF386
F3B0 SubCF3B0
F3CC SubCF3CC
F40B SubCF40B
F45C SubCF45C
F465 SubCF465
F470 SubCF470
F4A5 SubCF4A5
F504 SubCF504
F531 SubCF531
F561 SubCF561
F575 SubCF575
F5B2 SubCF5B2
F683 SubCF683
F687 SubCF687
F68B SubCF68B
F68F SubCF68F
F6A8 SubCF6A8
F712 SubCF712
F71A SubCF71A
F725 SubCF725
F758 SubCF758
F77C SubCF77C
F78F SubCF78F
F798 SubCF798
F824 SubCF824
F879 SubCF879
F89B SubCF89B
F8A6 SubCF8A6
F8BF SubCF8BF
F8CA SubCF8CA
F90A SubCF90A
F9BD SubCF9BD
FA38 SubCFA38
FAAC SubCFAAC
FB25 SubCFB25
FFF7 SubCFFF7
# ---- derived internal branch-target names ----
C000 Reset
C008 SubCC008_OnNonnegative
C00D SubCC00D_OnNegative
C012 SubCC012_OnNonnegative
C020 SubCC020_OnNonzero
C027 SubCC027_OnNonnegative
C034 SubCC034_Loop
C037 SubCC037_OnNonzero
C043 SubCC043_OnNonzero
C055 SubCC055_OnNonnegative
C060 SubCC060_OnNonnegative
C06E SubCC06E_OnNonnegative
C077 SubCC077_Loop
C094 NmiHandler
C0AC SubCC0AC_Loop
C0D1 SubCC0D1_OnNegative
C0DA SubCC0DA_OnNonzero
C0F1 SubCC0F1_Loop
C0F7 IrqHandler
C0FA SubCC0FA
C0FE SubCC0FE_OnNonzero
C104 SubCC104
C10A SubCC10A
C10C SubCC10C_OnNonzero
C115 SubCC115
C119 SubCC119
C11E SubCC11E_OnNonzero
C12D SubCC12D
C131 SubCC131
C144 SubCC144_OnNonzero
C154 SubCC154
C17C SubCC17C
C188 SubCC188_OnNonzero
C19E SubCC19E_OnNonzero
C1BE SubCC1BE_Loop
C1C5 SubCC1C5
C1FC SubCC1FC_OnNonnegative
C209 SubCC209
C216 SubCC216_Loop
C21E SubCC21E_Loop
C227 SubCC227_Loop
C231 SubCC231_Loop
C247 SubCC247_Loop
C24D SubCC24D_Loop
C24F SubCC24F_OnNonnegative
C26D SubCC26D_Loop
C272 SubCC272_OnNonnegative
C289 SubCC289_Loop
C2BC SubCC2BC_Loop
C2D0 SubCC2D0_Loop
C2D2 SubCC2D2_OnNonnegative
C2EF SubCC2EF_Loop
C2F7 SubCC2F7_OnNonnegative
C30D SubCC30D_Loop
C314 SubCC314_Loop
C317 SubCC317_Loop
C32D SubCC32D_Loop
C36F SubCC36F_Loop
C378 SubCC378_Loop
C3A1 SubCC3A1_Loop
C3B2 SubCC3B2
C3F7 SubCC3F7_OnNonzero
C405 SubCC405
C40C SubCC40C_Loop
C439 SubCC439_Loop
C43E SubCC43E
C454 SubCC454
C46B SubCC46B
C46D SubCC46D_OnNonnegative
C476 SubCC476_Loop
C486 SubCC486
C488 SubCC488_OnNonnegative
C491 SubCC491_Loop
C527 SubCC527
C539 SubCC539
C53D SubCC53D_OnNonzero
C54B SubCC54B_OnNonnegative
C559 SubCC559_Loop
C563 SubCC563_Loop
C579 SubCC579
C5A1 SubCC5A1_OnNonzero
C5AC SubCC5AC_Loop
C5AE SubCC5AE_OnNonnegative
C5C3 SubCC5C3
C5D5 SubCC5D5_Loop
C5D8 SubCC5D8
C5F4 SubCC5F4_Loop
C602 SubCC602_Loop
C607 SubCC607_Loop
C610 SubCC610_Loop
C613 SubCC613_Loop
C614 SubCC614
C61B SubCC61B_OnNonnegative
C62B SubCC62B_Loop
C62F SubCC62F_Loop
C64B SubCC64B
C657 SubCC657_Loop
C658 SubCC658
C66F SubCC66F_Loop
C671 SubCC671_Loop
C6A3 SubCC6A3_Loop
C6B3 SubCC6B3_Loop
C6B7 SubCC6B7_Loop
C6C4 SubCC6C4
C6E0 SubCC6E0_Loop
C6EE SubCC6EE_Loop
C6F8 SubCC6F8_Loop
C6F9 SubCC6F9
C709 SubCC709_Loop
C70D SubCC70D_Loop
C716 SubCC716
C718 SubCC718_OnNonnegative
C726 SubCC726
C72E SubCC72E_Loop
C77A SubCC77A
C77E SubCC77E_OnZero
C781 SubCC781_Loop
C784 SubCC784
C790 SubCC790
C796 SubCC796_OnNonzero
C797 SubCC797_Loop
C7AD SubCC7AD_Loop
C7B4 SubCC7B4_Loop
C811 SubCC811_Loop
C819 SubCC819_Loop
C821 SubCC821_Loop
C831 SubCC831
C846 SubCC846_Loop
C856 SubCC856_Loop
C883 SubCC883
C88A SubCC88A_Loop
C8B7 SubCC8B7
C8B9 SubCC8B9
C8C1 SubCC8C1_Loop
C8FF SubCC8FF_Loop
C937 SubCC937_Loop
C941 SubCC941_Loop
C94E SubCC94E_Loop
C958 SubCC958_Loop
C962 SubCC962_Loop
C976 SubCC976_Loop
C9AC SubCC9AC_Loop
C9AF SubCC9AF
C9B5 SubCC9B5_Loop
C9B6 SubCC9B6
CA37 SubCCA37
CA3D SubCCA3D
CA4F SubCCA4F
CA55 SubCCA55
CA67 SubCCA67
CA69 SubCCA69
CA82 SubCCA82_Loop
CA92 SubCCA92_Loop
CAA2 SubCCAA2_Loop
CAA9 SubCCAA9_Loop
CAAD SubCCAAD_Loop
CAC8 SubCCAC8_Loop
CADB SubCCADB_Loop
CADD SubCCADD_Loop
CAE1 SubCCAE1
CAE7 SubCCAE7_Loop
CAE8 SubCCAE8_Loop
CAF4 SubCCAF4_Loop
CB00 SubCCB00_Loop
CB0C SubCCB0C_Loop
CB18 SubCCB18_Loop
CB1C SubCCB1C
CB1E SubCCB1E_OnNonnegative
CB70 SubCCB70_Loop
CB74 SubCCB74
CB79 SubCCB79_OnNonnegative
CBA4 SubCCBA4_Loop
CBA7 SubCCBA7_Loop
CBA8 SubCCBA8
CBB2 SubCCBB2_OnNonnegative
CBC1 SubCCBC1_Loop
CBFC SubCCBFC_Loop
CC0B SubCCC0B_Loop
CC20 SubCCC20_Loop
CC2F SubCCC2F_Loop
CC33 SubCCC33
CC3A SubCCC3A
CC73 SubCCC73_Loop
CCA2 SubCCCA2_Loop
CCB8 SubCCCB8_Loop
CCBE SubCCCBE_Loop
CCBF SubCCCBF
CCCB SubCCCCB
CD0F SubCCD0F
CD25 SubCCD25_Loop
CD4A SubCCD4A
CD4C SubCCD4C_OnNonnegative
CD5A SubCCD5A
CD60 SubCCD60_Loop
CD6B SubCCD6B_OnNonnegative
CD74 SubCCD74_Loop
CDA2 SubCCDA2_Loop
CDAA SubCCDAA
CDAC SubCCDAC
CDFC SubCCDFC_Loop
CE0B SubCCE0B_Loop
CE1D SubCCE1D_Loop
CE22 SubCCE22_Loop
CE2E SubCCE2E_Loop
CE2F SubCCE2F
CE99 SubCCE99_Loop
CECE SubCCECE
CED0 SubCCED0_OnNonnegative
CF0F SubCCF0F_Loop
CF12 SubCCF12_Loop
CF13 SubCCF13
CF1F SubCCF1F_OnNonnegative
CF26 SubCCF26_Loop
CF34 SubCCF34_OnNonzero
CF47 SubCCF47_Loop
CF51 SubCCF51_OnNonnegative
CF7E SubCCF7E_OnNonnegative
CFB5 SubCCFB5_OnNonnegative
CFE8 SubCCFE8_Loop
D013 SubCD013_Loop
D01D SubCD01D_OnNonnegative
D02E SubCD02E_OnNonnegative
D04F SubCD04F_OnNonnegative
D068 SubCD068_Loop
D070 SubCD070_OnNonzero
D08E SubCD08E_Loop
D0A8 SubCD0A8_Loop
D0C0 SubCD0C0_OnNonnegative
D0CE SubCD0CE_Loop
D0D6 SubCD0D6_OnNonnegative
D0DC SubCD0DC_Loop
D0E2 SubCD0E2
D104 SubCD104_Loop
D121 SubCD121
D1A0 SubCD1A0
D1A2 SubCD1A2_OnNonnegative
D1C2 SubCD1C2_Loop
D1C9 SubCD1C9
D1CB SubCD1CB
D1D5 SubCD1D5_Loop
D1DC SubCD1DC
D1ED SubCD1ED_Loop
D1FB SubCD1FB_Loop
D1FE SubCD1FE_Loop
D200 SubCD200_OnNonzero
D208 SubCD208_Loop
D212 SubCD212_Loop
D213 SubCD213
D232 SubCD232_Loop
D238 SubCD238_Loop
D243 SubCD243_Loop
D246 SubCD246
D268 SubCD268_OnNonnegative
D275 SubCD275
D279 SubCD279_OnNonzero
D28C SubCD28C_OnNonzero
D293 SubCD293
D2A0 SubCD2A0_Loop
D2B1 SubCD2B1
D2C1 SubCD2C1_OnNonnegative
D2CB SubCD2CB_OnNonzero
D322 SubCD322_Loop
D327 SubCD327
D37E SubCD37E_Loop
D399 SubCD399_Loop
D39A SubCD39A_OnNonnegative
D3BA SubCD3BA
D3E1 SubCD3E1
D3ED SubCD3ED
D3EF SubCD3EF_OnNonnegative
D404 SubCD404_OnNonnegative
D40D SubCD40D_OnNonzero
D410 SubCD410_Loop
D421 SubCD421_OnNonnegative
D42D SubCD42D_OnNonnegative
D468 SubCD468
D48C SubCD48C
D492 SubCD492_Loop
D497 SubCD497_OnZero
D4A4 SubCD4A4_OnZero
D4CC SubCD4CC_OnNonzero
D4D8 SubCD4D8_Loop
D4DB SubCD4DB_OnNonzero
D4E4 SubCD4E4_Loop
D4E5 SubCD4E5
D4EF SubCD4EF_Loop
D4F0 SubCD4F0
D4FA SubCD4FA_Loop
D4FB SubCD4FB
D51C SubCD51C
D53C SubCD53C
D56C SubCD56C
D572 SubCD572
D593 SubCD593
D59B SubCD59B_OnNonzero
D5B1 SubCD5B1_OnNonzero
D5B8 SubCD5B8
D5C9 SubCD5C9
D5CB SubCD5CB_OnNonzero
D5D9 SubCD5D9
D5DB SubCD5DB_OnNonzero
D5F1 SubCD5F1
D60C SubCD60C_Loop
D60D SubCD60D
D632 SubCD632_OnNonnegative
D63A SubCD63A_Loop
D63B SubCD63B_Loop
D651 SubCD651
D6DC SubCD6DC
D6DE SubCD6DE
D6E4 SubCD6E4_OnNegative
D6E5 SubCD6E5_Loop
D746 SubCD746_OnNonnegative
D752 SubCD752_Loop
D75B SubCD75B_OnNonzero
D765 SubCD765_Loop
D767 SubCD767_OnNonnegative
D778 SubCD778_Loop
D77C SubCD77C
D782 SubCD782_OnCarrySet
D78F SubCD78F
D794 SubCD794_Loop
D798 SubCD798
D7A0 SubCD7A0_Loop
D7B1 SubCD7B1_OnNonnegative
D7D1 SubCD7D1_OnNonnegative
D7F5 SubCD7F5_OnNonnegative
D802 SubCD802_Loop
D805 SubCD805_Loop
D826 SubCD826
D828 SubCD828_OnZero
D82C SubCD82C_OnNonnegative
D834 SubCD834_Loop
D83A SubCD83A_Loop
D83B SubCD83B_Loop
D841 SubCD841_OnNonnegative
D854 SubCD854_Loop
D856 SubCD856_OnNonnegative
D871 SubCD871
D879 SubCD879_OnNonnegative
D88C SubCD88C_Loop
D8DD SubCD8DD
D8DF SubCD8DF_OnNonnegative
D8FB SubCD8FB_Loop
D8FF SubCD8FF
D901 SubCD901_OnNonnegative
D90F SubCD90F
DAC1 SubCDAC1_OnZero
DACB SubCDACB
DAED SubCDAED_Loop
DAF0 SubCDAF0_Loop
DAF1 SubCDAF1_Loop
DB08 SubCDB08
E3A4 SubCE3A4
E3B3 SubCE3B3_Loop
E3C2 SubCE3C2_OnNegative
E3C4 SubCE3C4_OnNonnegative
E3CF SubCE3CF_Loop
E408 SubCE408_Loop
E41B SubCE41B_Loop
E429 SubCE429_Loop
E43C SubCE43C_Loop
E444 SubCE444_Loop
E44B SubCE44B_Loop
E459 SubCE459_Loop
E463 SubCE463_Loop
E465 SubCE465_Loop
E47C SubCE47C_Loop
E486 SubCE486_Loop
E494 SubCE494_Loop
E49A SubCE49A_OnNonnegative
E4B1 SubCE4B1_Loop
E4CA SubCE4CA_Loop
E4D5 SubCE4D5
E50D SubCE50D_Loop
E54A SubCE54A_Loop
E550 SubCE550_Loop
E553 SubCE553_Loop
E584 SubCE584_Loop
E587 SubCE587
E599 SubCE599_OnNonzero
E5A7 SubCE5A7_Loop
E5AD SubCE5AD_OnNonnegative
E5C4 SubCE5C4_Loop
E691 SubCE691
E696 SubCE696_OnNonnegative
E6A4 SubCE6A4_Loop
E6B8 SubCE6B8_Loop
E6CE SubCE6CE_Loop
E6D9 SubCE6D9_Loop
E6E2 SubCE6E2_Loop
E6E9 SubCE6E9
E6F8 SubCE6F8_Loop
E704 SubCE704_OnNonzero
E705 SubCE705_Loop
E712 SubCE712_Loop
E749 SubCE749_Loop
E74D SubCE74D_Loop
E75B SubCE75B_Loop
E768 SubCE768
E76A SubCE76A
E776 SubCE776_OnNonnegative
E796 SubCE796
E79A SubCE79A_OnCarrySet
E7A3 SubCE7A3_Loop
E7B1 SubCE7B1
E7E8 SubCE7E8_Loop
E7EF SubCE7EF_Loop
E802 SubCE802_Loop
E80D SubCE80D_Loop
E811 SubCE811_Loop
E821 SubCE821_Loop
E829 SubCE829_Loop
E82E SubCE82E_Loop
E832 SubCE832_Loop
E845 SubCE845_Loop
E850 SubCE850_Loop
E854 SubCE854_Loop
E864 SubCE864_Loop
E874 SubCE874_Loop
E87C SubCE87C_Loop
E87F SubCE87F_Loop
E8A6 SubCE8A6_Loop
E8B8 SubCE8B8_Loop
E8C7 SubCE8C7_Loop
E8D1 SubCE8D1_Loop
E8EC SubCE8EC_Loop
E901 SubCE901
E907 SubCE907_Loop
E929 SubCE929_Loop
E93E SubCE93E
E951 SubCE951_Loop
E963 SubCE963_Loop
E968 SubCE968_Loop
E976 SubCE976_Loop
E982 SubCE982_Loop
E983 SubCE983
E99A SubCE99A_Loop
E9A4 SubCE9A4_Loop
E9B6 SubCE9B6_Loop
E9F2 SubCE9F2_Loop
E9F3 SubCE9F3_Loop
E9FD SubCE9FD_Loop
EA13 SubCEA13_Loop
EA15 SubCEA15_Loop
EA17 SubCEA17_Loop
EA18 SubCEA18
EA2C SubCEA2C_Loop
EA3E SubCEA3E_Loop
EA44 SubCEA44_Loop
EA47 SubCEA47_Loop
EA57 SubCEA57_Loop
EA58 SubCEA58
EA60 SubCEA60_Loop
EA8B SubCEA8B_Loop
EA8C SubCEA8C_Loop
EA9E SubCEA9E_Loop
EAB2 SubCEAB2_Loop
EAC1 SubCEAC1_Loop
EAD0 SubCEAD0_Loop
EADC SubCEADC_Loop
EB05 SubCEB05_Loop
EB0D SubCEB0D_Loop
EB21 SubCEB21_Loop
EB30 SubCEB30_Loop
EB3F SubCEB3F_Loop
EB4B SubCEB4B_Loop
EB5A SubCEB5A_Loop
EB60 SubCEB60_Loop
EB62 SubCEB62_Loop
EB84 SubCEB84_Loop
EB8D SubCEB8D_Loop
EB8E SubCEB8E
EBA0 SubCEBA0
EBB2 SubCEBB2
EBBB SubCEBBB
EBC4 SubCEBC4
EBD6 SubCEBD6_Loop
EBE3 SubCEBE3_Loop
EBF7 SubCEBF7_Loop
EBFD SubCEBFD_OnCarryClear
EBFE SubCEBFE_Loop
EC2F SubCEC2F_Loop
EC37 SubCEC37_Loop
EC38 SubCEC38_Loop
EC49 SubCEC49_Loop
EC5C SubCEC5C_Loop
EC61 SubCEC61_Loop
EC75 SubCEC75_Loop
EC7E SubCEC7E_Loop
EC93 SubCEC93_Loop
ECAD SubCECAD_Loop
ECBA SubCECBA
ECDB SubCECDB_Loop
ECDF SubCECDF_OnNonnegative
ED22 SubCED22_Loop
ED27 SubCED27_OnNegative
ED28 SubCED28
ED2D SubCED2D_OnNonnegative
ED2E SubCED2E_Loop
ED40 SubCED40_Loop
ED44 SubCED44
ED5B SubCED5B_Loop
ED69 SubCED69_Loop
ED78 SubCED78_Loop
ED85 SubCED85_Loop
ED89 SubCED89_Loop
EDA0 SubCEDA0_Loop
EDB4 SubCEDB4_Loop
EDB6 SubCEDB6_Loop
EDC0 SubCEDC0_Loop
EDC1 SubCEDC1_Loop
EDD6 SubCEDD6_Loop
EDE1 SubCEDE1
EDF0 SubCEDF0_Loop
EDF4 SubCEDF4_Loop
EDFF SubCEDFF_Loop
EE08 SubCEE08_Loop
EE24 SubCEE24_Loop
EE25 SubCEE25
EE27 SubCEE27
EE2E SubCEE2E_OnZero
EE31 SubCEE31_Loop
EE6A SubCEE6A_Loop
EE7C SubCEE7C_Loop
EE8F SubCEE8F_Loop
EEAA SubCEEAA_Loop
EEBC SubCEEBC_Loop
EEC0 SubCEEC0_Loop
EECD SubCEECD_Loop
EED6 SubCEED6_Loop
EEED SubCEEED_Loop
EEF1 SubCEEF1_Loop
EEFA SubCEEFA_Loop
EF03 SubCEF03_Loop
EF1A SubCEF1A_Loop
EF1E SubCEF1E_Loop
EF2A SubCEF2A
EF30 SubCEF30_Loop
EF36 SubCEF36_Loop
EF37 SubCEF37
EF42 SubCEF42_Loop
EF4F SubCEF4F_Loop
EF56 SubCEF56_Loop
EF61 SubCEF61_Loop
EF72 SubCEF72_Loop
EF7F SubCEF7F_Loop
EF97 SubCEF97_Loop
EFB7 SubCEFB7_Loop
EFC0 SubCEFC0_Loop
EFCE SubCEFCE_Loop
EFE0 SubCEFE0_Loop
EFE2 SubCEFE2_Loop
EFEA SubCEFEA_Loop
F011 SubCF011_Loop
F023 SubCF023_Loop
F043 SubCF043_Loop
F052 SubCF052_Loop
F08E SubCF08E
F097 SubCF097_Loop
F098 SubCF098
F0A6 SubCF0A6
F0B4 SubCF0B4
F0BD SubCF0BD
F0DD SubCF0DD_Loop
F0DE SubCF0DE
F107 SubCF107
F119 SubCF119
F143 SubCF143_Loop
F14F SubCF14F_OnNonzero
F16C SubCF16C_Loop
F172 SubCF172
F18C SubCF18C
F1A6 SubCF1A6
F1A8 SubCF1A8_OnNonzero
F1B3 SubCF1B3
F1B7 SubCF1B7_OnNonzero
F1D4 SubCF1D4
F1D9 SubCF1D9_OnNonnegative
F1F2 SubCF1F2
F1FA SubCF1FA_Loop
F20D SubCF20D_OnNonnegative
F213 SubCF213
F221 SubCF221_Loop
F238 SubCF238_Loop
F23A SubCF23A_OnNonnegative
F26F SubCF26F_OnNonnegative
F278 SubCF278_OnNonnegative
F28E SubCF28E_Loop
F29B SubCF29B_Loop
F2A2 SubCF2A2_Loop
F2B3 SubCF2B3_Loop
F2B9 SubCF2B9_OnNonnegative
F2C5 SubCF2C5_Loop
F2E4 SubCF2E4_OnNonnegative
F30D SubCF30D_Loop
F318 SubCF318_Loop
F326 SubCF326_Loop
F327 SubCF327_Loop
F329 SubCF329_OnNonnegative
F32F SubCF32F_Loop
F338 SubCF338_OnNonnegative
F34C SubCF34C_Loop
F353 SubCF353
F361 SubCF361_Loop
F366 SubCF366_Loop
F36A SubCF36A
F375 SubCF375_OnNonzero
F383 SubCF383_Loop
F386 SubCF386
F3A1 SubCF3A1_Loop
F3AD SubCF3AD_Loop
F3B0 SubCF3B0
F3CC SubCF3CC
F3D4 SubCF3D4_OnNonnegative
F3EE SubCF3EE_Loop
F40B SubCF40B
F410 SubCF410_OnNonnegative
F41E SubCF41E_OnNonnegative
F42F SubCF42F_OnNonnegative
F45C SubCF45C
F45E SubCF45E_OnNonzero
F465 SubCF465
F469 SubCF469_OnZero
F46F SubCF46F_OnZero
F470 SubCF470
F489 SubCF489_OnZero
F4A2 SubCF4A2_Loop
F4A5 SubCF4A5
F500 SubCF500_OnZero
F503 SubCF503_OnZero
F504 SubCF504
F50B SubCF50B_OnZero
F50E SubCF50E_OnNonzero
F51B SubCF51B_Loop
F531 SubCF531
F547 SubCF547_Loop
F553 SubCF553_Loop
F55E SubCF55E_Loop
F561 SubCF561
F575 SubCF575
F57B SubCF57B_Loop
F587 SubCF587_OnZero
F599 SubCF599_Loop
F5AA SubCF5AA_Loop
F5AC SubCF5AC_Loop
F5B2 SubCF5B2
F5B9 SubCF5B9_Loop
F5C4 SubCF5C4_Loop
F5CE SubCF5CE_Loop
F5D9 SubCF5D9_Loop
F5E1 SubCF5E1_Loop
F5F9 SubCF5F9_Loop
F683 SubCF683
F687 SubCF687
F68B SubCF68B
F68F SubCF68F
F691 SubCF691_Loop
F69D SubCF69D_OnNonzero
F6A8 SubCF6A8
F6BE SubCF6BE_Loop
F6C4 SubCF6C4_OnNonzero
F712 SubCF712
F71A SubCF71A
F71F SubCF71F_OnNonzero
F725 SubCF725
F736 SubCF736_Loop
F745 SubCF745_Loop
F749 SubCF749_Loop
F758 SubCF758
F77B SubCF77B_OnNonzero
F77C SubCF77C
F78F SubCF78F
F798 SubCF798
F79F SubCF79F_Loop
F7A5 SubCF7A5_Loop
F7B4 SubCF7B4_OnZero
F7C7 SubCF7C7_Loop
F7D3 SubCF7D3_OnZero
F7D9 SubCF7D9_OnZero
F7E0 SubCF7E0_OnZero
F7EF SubCF7EF_OnZero
F800 SubCF800_OnCarrySet
F814 SubCF814_OnCarrySet
F821 SubCF821_OnCarrySet
F824 SubCF824
F83B SubCF83B_Loop
F85B SubCF85B_Loop
F85C SubCF85C_Loop
F85F SubCF85F_Loop
F879 SubCF879
F87D SubCF87D_Loop
F89B SubCF89B
F8A1 SubCF8A1_Loop
F8A2 SubCF8A2_Loop
F8A6 SubCF8A6
F8BF SubCF8BF
F8CA SubCF8CA
F8DD SubCF8DD_OnCarrySet
F8E8 SubCF8E8_Loop
F907 SubCF907_OnCarrySet
F90A SubCF90A
F91B SubCF91B_Loop
F94B SubCF94B_Loop
F94E SubCF94E_Loop
F94F SubCF94F_Loop
F952 SubCF952_Loop
F965 SubCF965_Loop
F977 SubCF977_Loop
F98F SubCF98F_Loop
F993 SubCF993_Loop
F9B1 SubCF9B1_Loop
F9BD SubCF9BD
F9CA SubCF9CA_Loop
F9E9 SubCF9E9_OnCarrySet
F9F9 SubCF9F9_Loop
FA0C SubCFA0C_OnCarrySet
FA26 SubCFA26_Loop
FA27 SubCFA27_OnCarrySet
FA38 SubCFA38
FA42 SubCFA42_Loop
FA63 SubCFA63_Loop
FA64 SubCFA64_Loop
FA7F SubCFA7F_Loop
FA83 SubCFA83_Loop
FA96 SubCFA96_OnCarrySet
FAAC SubCFAAC
FABA SubCFABA_Loop
FAD8 SubCFAD8_Loop
FAD9 SubCFAD9_Loop
FAE2 SubCFAE2_Loop
FB00 SubCFB00_Loop
FB04 SubCFB04_Loop
FB10 SubCFB10_Loop
FB17 SubCFB17_Loop
FB1E SubCFB1E_OnCarrySet
FB25 SubCFB25
FB49 SubCFB49_OnNonzero
FB4C SubCFB4C_Loop
FB52 SubCFB52_Loop
FB58 SubCFB58_Loop
FB5E SubCFB5E_Loop
FB69 SubCFB69_Loop
FB6D SubCFB6D_Loop
FB7C SubCFB7C_Loop
FB82 SubCFB82_Loop
FB86 SubCFB86_Loop
FB8D SubCFB8D_OnNonzero
FBA5 SubCFBA5_Loop
FBAC SubCFBAC_Loop
FBAF SubCFBAF_Loop
FBC1 SubCFBC1_Loop
FFF7 SubCFFF7