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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

PROMPTS.md gains two Pass 3 requirements:

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

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

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

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

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

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

All seven projects still build byte-identical.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Three lessons from the seven re-splits:

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

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

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

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

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

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

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

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

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

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

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

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

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

derive_routine_docs.py: describe what each routine actually does

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

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

Rewrite the routine headers across the promoted tier

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

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

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

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

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

CHANGELOG: record the tier-wide routine header rewrite

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

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

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

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

make still prints Byte-identical ROM verified.

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

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

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

Two real bugs are fixed on the way:

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

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

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

Complete Pass 2 across the tier: no Label_ residue left

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

Three more real defects in the tools are fixed:

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

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

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

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

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

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

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

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

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

apply_pass2_map.py: do not write the same equate twice

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

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

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

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

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

All 61 promoted projects now carry the section.

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

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

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

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

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

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

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

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

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

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

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

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

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

Repair the damaged audit trails across the tier

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

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

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

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

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

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

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

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

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

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

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

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

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

Give every routine header a contract that is its own

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Interpret the data tables across the tier

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

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: move the committed entries into History

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

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

Root README: refresh the coverage column of the project inventory

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

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

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

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

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

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

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

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

TODO.md: bring the handoff up to date

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

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

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

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

Three gaps it found, now closed:

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

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

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

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

Every project still prints Byte-identical ROM verified.

PROMPTS.md: the checklist now has a checker

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

CHANGELOG: record the checklist work

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the zero-page residue work

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

The promoted tier now passes every item of the promotion checklist

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

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

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

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

Every project still prints Byte-identical ROM verified.

CHANGELOG: record the tier passing the checklist

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

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

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

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

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

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

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

Every project still prints Byte-identical ROM verified.

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

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

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

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

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

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

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

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

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

Remaining entry-point naming

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

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

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

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

CHANGELOG: record the entry-point naming

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

Re-align the audit comments to the canonical column

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

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

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

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

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

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

CHANGELOG: record the audit-comment re-alignment

Remaining entry-point naming

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

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

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

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

CHANGELOG: record the tier reaching completion

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

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

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

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

Every project still prints Byte-identical ROM verified.

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

849 lines
15 KiB
Plaintext
Raw Blame History

8000 Reset
803A SubC803A
8069 SubC8069
80AC SubC80AC
815A SubC815A
815D SubC815D
81A2 SubC81A2
8219 SubC8219
82AA SubC82AA
82DD SubC82DD
8390 SubC8390
8399 SubC8399
83AD SubC83AD
8420 SubC8420
842B SubC842B
8444 SubC8444
8456 SubC8456
8471 NmiHandler
84F3 SubC84F3
84F6 SubC84F6
84FA SubC84FA
84FF IrqHandler
8500 SubC8500
853B SubC853B
8549 SubC8549
857F SubC857F
85B0 SubC85B0
85D6 SubC85D6
85EF SubC85EF
8839 SubC8839
888D SubC888D
88A1 SubC88A1
88C8 SubC88C8
88FB SubC88FB
8953 SubC8953
8999 SubC8999
89AD SubC89AD
89B7 SubC89B7
89C1 SubC89C1
8A95 SubC8A95
8B14 SubC8B14
8B5B SubC8B5B
8B73 SubC8B73
8B8E SubC8B8E
8BB8 SubC8BB8
8C30 SubC8C30
8C47 SubC8C47
8CA4 SubC8CA4
8CC2 SubC8CC2
8D28 SubC8D28
8D31 SubC8D31
8D67 SubC8D67
8D73 SubC8D73
8DBE SubC8DBE
8DE2 SubC8DE2
8E36 SubC8E36
8EC4 SubC8EC4
8EF1 SubC8EF1
8EFC SubC8EFC
8F00 SubC8F00
8F37 SubC8F37
8F4A SubC8F4A
8F59 SubC8F59
8F62 SubC8F62
8F6A SubC8F6A
8FFC SubC8FFC
902F SubC902F
903C SubC903C
908D SubC908D
90D2 SubC90D2
90FD SubC90FD
9109 SubC9109
9152 SubC9152
9179 SubC9179
927B SubC927B
9298 SubC9298
929E SubC929E
92AD SubC92AD
92B0 SubC92B0
9372 SubC9372
93DB SubC93DB
93EA SubC93EA
945F SubC945F
9465 SubC9465
9474 SubC9474
947B SubC947B
94DF SubC94DF
9586 SubC9586
95B7 SubC95B7
9633 SubC9633
968F SubC968F
96E8 SubC96E8
98F4 SubC98F4
998B SubC998B
99E0 SubC99E0
9A00 SubC9A00
9A1F SubC9A1F
9DD7 SubC9DD7
9E04 SubC9E04
9E77 SubC9E77
9ECF SubC9ECF
9F49 SubC9F49
9FA9 SubC9FA9
A00A SubCA00A
A038 SubCA038
A1D6 SubCA1D6
A24F SubCA24F
A278 SubCA278
A318 SubCA318
A348 SubCA348
A3C5 SubCA3C5
A3D8 SubCA3D8
A415 SubCA415
A534 SubCA534
A5D5 SubCA5D5
A779 SubCA779
A780 SubCA780
A798 SubCA798
A7B7 SubCA7B7
A8AA SubCA8AA
A905 SubCA905
A934 SubCA934
A946 SubCA946
A9A4 SubCA9A4
A9C8 SubCA9C8
A9D9 SubCA9D9
AACF SubCAACF
AAE4 SubCAAE4
AAF3 SubCAAF3
AC3E SubCAC3E
ADE2 SubCADE2
AE49 SubCAE49
AE5E SubCAE5E
AF04 SubCAF04
AF21 SubCAF21
AFAD SubCAFAD
B031 SubCB031
B03F SubCB03F
B097 SubCB097
B0AD SubCB0AD
B62C SubCB62C
B6D7 SubCB6D7
B703 SubCB703
B72D SubCB72D
B813 SubCB813
B872 SubCB872
B8A3 SubCB8A3
B8FC SubCB8FC
BE8D SubCBE8D
BEA3 SubCBEA3
BEB4 SubCBEB4
BEC5 SubCBEC5
BF19 SubCBF19
BF33 SubCBF33
BF47 SubCBF47
BFC3 SubCBFC3
BFD2 SubCBFD2
BFF7 SubCBFF7
BFFC SubCBFFC
C006 SubCC006
C016 SubCC016
C02E SubCC02E
C037 SubCC037
C05E SubCC05E
C076 SubCC076
C088 SubCC088
C09A SubCC09A
C0B1 SubCC0B1
C0C3 SubCC0C3
C0D5 SubCC0D5
C0E7 SubCC0E7
C0F1 SubCC0F1
C106 SubCC106
C113 SubCC113
C126 SubCC126
C133 SubCC133
C140 SubCC140
C14D SubCC14D
C157 SubCC157
C161 SubCC161
C16D SubCC16D
C337 SubCC337
C4F9 SubCC4F9
C543 SubCC543
C558 SubCC558
C56F SubCC56F
C5CF SubCC5CF
C5F3 SubCC5F3
C75F SubCC75F
C82B SubCC82B
C85A SubCC85A
C8AE SubCC8AE
C8EF SubCC8EF
CA15 SubCCA15
CA38 SubCCA38
CA59 SubCCA59
CB37 SubCCB37
CB67 SubCCB67
CBBC SubCCBBC
# ---- derived internal branch-target names ----
8000 Reset
8007 SubC8007_OnNonnegative
8012 SubC8012_OnNonnegative
803A SubC803A
8069 SubC8069
807A SubC807A_Loop
808D SubC808D_Loop
80A4 SubC80A4_Loop
80AC SubC80AC
811A SubC811A_OnNonzero
812D SubC812D_OnZero
8149 SubC8149_Loop
8151 SubC8151_Loop
815A SubC815A
815D SubC815D
8181 SubC8181_Loop
8194 SubC8194_Loop
81A2 SubC81A2
81A5 SubC81A5_Loop
81BE SubC81BE_OnZero
81E4 SubC81E4_OnNonzero
81FC SubC81FC_OnZero
8219 SubC8219
8228 SubC8228_Loop
822D SubC822D_Loop
8233 SubC8233_Loop
8275 SubC8275_OnNonzero
8289 SubC8289_OnZero
82A7 SubC82A7_Loop
82AA SubC82AA
82B8 SubC82B8_OnNegative
82D2 SubC82D2_Loop
82DD SubC82DD
82E9 SubC82E9_Loop
831E SubC831E_Loop
8390 SubC8390
8399 SubC8399
83AD SubC83AD
83B5 SubC83B5_Loop
83C0 SubC83C0_Loop
83C6 SubC83C6_Loop
8420 SubC8420
8424 SubC8424_OnNonzero
842B SubC842B
8441 SubC8441_Loop
8444 SubC8444
8456 SubC8456
8464 SubC8464_OnNonnegative
846E SubC846E_Loop
8471 NmiHandler
848A SubC848A_Loop
8493 SubC8493_Loop
84A5 SubC84A5_Loop
84AA SubC84AA_Loop
84B2 SubC84B2_Loop
84F3 SubC84F3
84F6 SubC84F6
84FA SubC84FA
84FF IrqHandler
8500 SubC8500
851E SubC851E_Loop
8531 SubC8531_Loop
853A SubC853A_Loop
853B SubC853B
853D SubC853D_OnNonnegative
8549 SubC8549
854B SubC854B_OnNonnegative
857F SubC857F
858A SubC858A_Loop
858E SubC858E_OnNegative
8595 SubC8595_Loop
85AF SubC85AF_Loop
85B0 SubC85B0
85BF SubC85BF_Loop
85CE SubC85CE_Loop
85D6 SubC85D6
85E4 SubC85E4_Loop
85EC SubC85EC_Loop
85EF SubC85EF
8602 SubC8602_Loop
8604 SubC8604_OnCarryClear
8612 SubC8612_OnCarryClear
8644 SubC8644_Loop
865F SubC865F_OnCarrySet
866A SubC866A_OnNonnegative
868E SubC868E_Loop
8839 SubC8839
8850 SubC8850_OnCarryClear
8856 SubC8856_OnCarryClear
8866 SubC8866_Loop
887D SubC887D_Loop
888D SubC888D
88A0 SubC88A0_Loop
88A1 SubC88A1
88B5 SubC88B5_Loop
88C0 SubC88C0_Loop
88C8 SubC88C8
88CA SubC88CA_OnNonnegative
88F3 SubC88F3_OnCarrySet
88FB SubC88FB
8902 SubC8902_OnNonzero
8910 SubC8910_OnZero
892B SubC892B_Loop
893D SubC893D_Loop
8946 SubC8946_Loop
8953 SubC8953
8979 SubC8979_Loop
8991 SubC8991_Loop
8999 SubC8999
89A4 SubC89A4_Loop
89A8 SubC89A8_Loop
89AA SubC89AA_Loop
89AD SubC89AD
89B7 SubC89B7
89C1 SubC89C1
89E6 SubC89E6_Loop
89ED SubC89ED_OnZero
8A11 SubC8A11_Loop
8A1E SubC8A1E_OnNonzero
8A3E SubC8A3E_Loop
8A4E SubC8A4E_OnNonzero
8A55 SubC8A55_Loop
8A85 SubC8A85_OnNonzero
8A8C SubC8A8C_Loop
8A95 SubC8A95
8A9D SubC8A9D_Loop
8AA0 SubC8AA0_OnCarryClear
8B14 SubC8B14
8B3D SubC8B3D_Loop
8B5A SubC8B5A_Loop
8B5B SubC8B5B
8B6F SubC8B6F_Loop
8B70 SubC8B70_Loop
8B73 SubC8B73
8B8E SubC8B8E
8BA6 SubC8BA6_Loop
8BB1 SubC8BB1_OnNonzero
8BB8 SubC8BB8
8BF6 SubC8BF6_Loop
8C19 SubC8C19_Loop
8C2A SubC8C2A_Loop
8C30 SubC8C30
8C42 SubC8C42_Loop
8C44 SubC8C44_Loop
8C47 SubC8C47
8C5A SubC8C5A_Loop
8CA4 SubC8CA4
8CC0 SubC8CC0_Loop
8CC2 SubC8CC2
8D28 SubC8D28
8D2F SubC8D2F_Loop
8D31 SubC8D31
8D43 SubC8D43_Loop
8D4E SubC8D4E_Loop
8D60 SubC8D60_Loop
8D67 SubC8D67
8D72 SubC8D72_Loop
8D73 SubC8D73
8D75 SubC8D75_OnCarryClear
8DBC SubC8DBC_Loop
8DBE SubC8DBE
8DC7 SubC8DC7_OnCarryClear
8DE2 SubC8DE2
8DFB SubC8DFB_Loop
8E1D SubC8E1D_Loop
8E35 SubC8E35_Loop
8E36 SubC8E36
8E4E SubC8E4E_OnNonzero
8E93 SubC8E93_Loop
8E94 SubC8E94_Loop
8EB7 SubC8EB7_Loop
8EC4 SubC8EC4
8ED4 SubC8ED4_OnNonzero
8EDE SubC8EDE_OnCarryClear
8EE8 SubC8EE8_OnNonzero
8EF1 SubC8EF1
8EF5 SubC8EF5_OnNonzero
8EFC SubC8EFC
8F00 SubC8F00
8F02 SubC8F02_Loop
8F17 SubC8F17_OnCarryClear
8F37 SubC8F37
8F4A SubC8F4A
8F59 SubC8F59
8F62 SubC8F62
8F6A SubC8F6A
8F81 SubC8F81_OnNonzero
8F9B SubC8F9B_OnNonzero
8FB5 SubC8FB5_OnNonzero
8FCF SubC8FCF_Loop
8FFC SubC8FFC
901A SubC901A_OnCarryClear
901B SubC901B_Loop
902F SubC902F
903C SubC903C
9048 SubC9048_Loop
906C SubC906C_OnCarryClear
907B SubC907B_Loop
907F SubC907F_Loop
9081 SubC9081_OnCarryClear
908D SubC908D
90AF SubC90AF_OnNonnegative
90B1 SubC90B1_OnCarryClear
90C1 SubC90C1_OnCarryClear
90D2 SubC90D2
90D4 SubC90D4_OnNonnegative
90D6 SubC90D6_OnCarryClear
90FD SubC90FD
9109 SubC9109
9111 SubC9111_OnNonnegative
9121 SubC9121_Loop
9123 SubC9123_OnNonnegative
912E SubC912E_OnNonnegative
9146 SubC9146_Loop
9152 SubC9152
9165 SubC9165_OnNonzero
9171 SubC9171_Loop
9179 SubC9179
9194 SubC9194_Loop
91A9 SubC91A9_Loop
91AE SubC91AE_Loop
91B0 SubC91B0_Loop
927B SubC927B
9298 SubC9298
929E SubC929E
92A0 SubC92A0_OnNonzero
92AD SubC92AD
92B0 SubC92B0
92B2 SubC92B2_OnNonzero
92D3 SubC92D3_OnCarryClear
9372 SubC9372
93B5 SubC93B5_Loop
93DB SubC93DB
93EA SubC93EA
93ED SubC93ED_OnNonzero
9440 SubC9440_Loop
9450 SubC9450_Loop
9452 SubC9452_Loop
9457 SubC9457_Loop
945E SubC945E_Loop
945F SubC945F
9465 SubC9465
9467 SubC9467_OnCarryClear
9474 SubC9474
947B SubC947B
9483 SubC9483_Loop
94BB SubC94BB_Loop
94CB SubC94CB_Loop
94CD SubC94CD_Loop
94DC SubC94DC_OnNegative
94DF SubC94DF
94FE SubC94FE_OnCarryClear
950B SubC950B_Loop
9510 SubC9510_OnCarryClear
9547 SubC9547_OnCarryClear
9569 SubC9569_Loop
957C SubC957C_Loop
9586 SubC9586
958E SubC958E_Loop
95A0 SubC95A0_Loop
95AF SubC95AF_Loop
95B7 SubC95B7
95CA SubC95CA_OnNonzero
95D7 SubC95D7_Loop
95F5 SubC95F5_OnCarryClear
9603 SubC9603_OnNonzero
960F SubC960F_Loop
9613 SubC9613_Loop
9627 SubC9627_Loop
9629 SubC9629_OnNonnegative
9633 SubC9633
9647 SubC9647_OnNonnegative
9664 SubC9664_OnCarryClear
967B SubC967B_Loop
968F SubC968F
9691 SubC9691_OnNonnegative
96A3 SubC96A3_Loop
96BF SubC96BF_Loop
96CA SubC96CA_Loop
96E8 SubC96E8
96FF SubC96FF_Loop
970C SubC970C_Loop
9718 SubC9718_OnCarryClear
9747 SubC9747_Loop
9756 SubC9756_OnCarryClear
9785 SubC9785_Loop
97A9 SubC97A9_Loop
97AB SubC97AB_Loop
97C0 SubC97C0_Loop
97C2 SubC97C2_Loop
97C5 SubC97C5_OnCarryClear
97FB SubC97FB_Loop
980C SubC980C_Loop
9871 SubC9871_Loop
988C SubC988C_Loop
98F4 SubC98F4
9902 SubC9902_OnCarryClear
990B SubC990B_Loop
9926 SubC9926_OnCarryClear
998B SubC998B
998D SubC998D_OnCarryClear
99A0 SubC99A0_Loop
99A7 SubC99A7_OnCarryClear
99E0 SubC99E0
9A00 SubC9A00
9A06 SubC9A06_OnNonnegative
9A10 SubC9A10_OnNonnegative
9A1F SubC9A1F
9DD7 SubC9DD7
9DE1 SubC9DE1_OnNonzero
9DF3 SubC9DF3_Loop
9E04 SubC9E04
9E06 SubC9E06_OnNonnegative
9E18 SubC9E18_Loop
9E22 SubC9E22_OnNonnegative
9E2D SubC9E2D_Loop
9E30 SubC9E30_Loop
9E77 SubC9E77
9E87 SubC9E87_Loop
9E8B SubC9E8B_Loop
9EB3 SubC9EB3_Loop
9EC6 SubC9EC6_Loop
9ECF SubC9ECF
9F02 SubC9F02_Loop
9F16 SubC9F16_Loop
9F21 SubC9F21_Loop
9F2A SubC9F2A_Loop
9F36 SubC9F36_Loop
9F3F SubC9F3F_Loop
9F49 SubC9F49
9F5F SubC9F5F_Loop
9F83 SubC9F83_OnNonnegative
9FA9 SubC9FA9
A00A SubCA00A
A02E SubCA02E_Loop
A030 SubCA030_Loop
A038 SubCA038
A03D SubCA03D_OnCarryClear
A03F SubCA03F_OnCarryClear
A054 SubCA054_Loop
A05C SubCA05C_OnCarryClear
A1D6 SubCA1D6
A1F3 SubCA1F3_Loop
A214 SubCA214_Loop
A224 SubCA224_Loop
A239 SubCA239_Loop
A24E SubCA24E_Loop
A24F SubCA24F
A26C SubCA26C_Loop
A278 SubCA278
A283 SubCA283_Loop
A289 SubCA289_Loop
A290 SubCA290_Loop
A297 SubCA297_Loop
A318 SubCA318
A31A SubCA31A_OnCarryClear
A331 SubCA331_OnCarryClear
A348 SubCA348
A356 SubCA356_Loop
A375 SubCA375_Loop
A38A SubCA38A_Loop
A398 SubCA398_Loop
A39E SubCA39E_Loop
A3A2 SubCA3A2_Loop
A3C5 SubCA3C5
A3D3 SubCA3D3_Loop
A3D8 SubCA3D8
A3E0 SubCA3E0_OnNonnegative
A415 SubCA415
A43A SubCA43A_Loop
A43F SubCA43F_Loop
A451 SubCA451_Loop
A534 SubCA534
A545 SubCA545_Loop
A548 SubCA548_Loop
A55A SubCA55A_OnCarryClear
A56F SubCA56F_OnCarryClear
A589 SubCA589_OnCarryClear
A5D5 SubCA5D5
A5E7 SubCA5E7_OnCarryClear
A60B SubCA60B_Loop
A611 SubCA611_Loop
A779 SubCA779
A780 SubCA780
A798 SubCA798
A7A5 SubCA7A5_OnNonnegative
A7B7 SubCA7B7
A7CB SubCA7CB_Loop
A7CC SubCA7CC_Loop
A7D2 SubCA7D2_Loop
A7DB SubCA7DB_Loop
A7DD SubCA7DD_Loop
A8AA SubCA8AA
A8B4 SubCA8B4_Loop
A8E1 SubCA8E1_OnCarryClear
A904 SubCA904_Loop
A905 SubCA905
A90D SubCA90D_Loop
A929 SubCA929_Loop
A933 SubCA933_Loop
A934 SubCA934
A946 SubCA946
A94E SubCA94E_Loop
A980 SubCA980_OnNonzero
A9A4 SubCA9A4
A9C8 SubCA9C8
A9D9 SubCA9D9
A9E8 SubCA9E8_OnNonnegative
AA07 SubCAA07_Loop
AA0D SubCAA0D_OnCarrySet
AA2A SubCAA2A_Loop
AA36 SubCAA36_Loop
AA43 SubCAA43_Loop
AA47 SubCAA47_OnNonzero
AA54 SubCAA54_Loop
AA6C SubCAA6C_OnCarryClear
AA73 SubCAA73_Loop
AA7B SubCAA7B_OnCarryClear
AA82 SubCAA82_Loop
AA98 SubCAA98_Loop
AACF SubCAACF
AADE SubCAADE_Loop
AAE4 SubCAAE4
AAF3 SubCAAF3
AC3E SubCAC3E
AC52 SubCAC52_Loop
AC79 SubCAC79_Loop
ADE2 SubCADE2
AE01 SubCAE01_Loop
AE1B SubCAE1B_Loop
AE1C SubCAE1C_Loop
AE24 SubCAE24_Loop
AE37 SubCAE37_Loop
AE3D SubCAE3D_Loop
AE49 SubCAE49
AE5E SubCAE5E
AE60 SubCAE60_OnCarryClear
AF04 SubCAF04
AF21 SubCAF21
AF23 SubCAF23_OnNonnegative
AF3D SubCAF3D_Loop
AFAD SubCAFAD
AFB6 SubCAFB6_Loop
AFC6 SubCAFC6_OnCarryClear
AFD4 SubCAFD4_Loop
AFDB SubCAFDB_Loop
AFE6 SubCAFE6_Loop
AFEB SubCAFEB_Loop
AFF2 SubCAFF2_Loop
B031 SubCB031
B03E SubCB03E_OnNonnegative
B03F SubCB03F
B047 SubCB047_Loop
B04E SubCB04E_OnNonzero
B06C SubCB06C_Loop
B077 SubCB077_Loop
B07A SubCB07A_Loop
B085 SubCB085_Loop
B097 SubCB097
B0A9 SubCB0A9_Loop
B0AD SubCB0AD
B0CA SubCB0CA_Loop
B0EB SubCB0EB_Loop
B0FB SubCB0FB_Loop
B110 SubCB110_Loop
B125 SubCB125_Loop
B62C SubCB62C
B63A SubCB63A_Loop
B63D SubCB63D_Loop
B643 SubCB643_Loop
B656 SubCB656_Loop
B674 SubCB674_Loop
B682 SubCB682_Loop
B695 SubCB695_Loop
B697 SubCB697_Loop
B6A9 SubCB6A9_Loop
B6AB SubCB6AB_Loop
B6B3 SubCB6B3_Loop
B6D6 SubCB6D6_Loop
B6D7 SubCB6D7
B6E4 SubCB6E4_Loop
B702 SubCB702_Loop
B703 SubCB703
B710 SubCB710_Loop
B72C SubCB72C_Loop
B72D SubCB72D
B76B SubCB76B_Loop
B78E SubCB78E_Loop
B7BF SubCB7BF_Loop
B7C7 SubCB7C7_Loop
B7DE SubCB7DE_Loop
B7E3 SubCB7E3_Loop
B813 SubCB813
B832 SubCB832_Loop
B843 SubCB843_Loop
B856 SubCB856_Loop
B871 SubCB871_Loop
B872 SubCB872
B89D SubCB89D_Loop
B8A0 SubCB8A0_Loop
B8A3 SubCB8A3
B8B4 SubCB8B4_OnCarrySet
B8B5 SubCB8B5_OnOverflowSet
B8EB SubCB8EB_Loop
B8F6 SubCB8F6_OnNegative
B8FC SubCB8FC
B90C SubCB90C_Loop
B90E SubCB90E_OnCarryClear
B929 SubCB929_Loop
B92E SubCB92E_Loop
B944 SubCB944_Loop
BE8D SubCBE8D
BEA3 SubCBEA3
BEB4 SubCBEB4
BEC5 SubCBEC5
BED8 SubCBED8_Loop
BED9 SubCBED9_Loop
BEE0 SubCBEE0_Loop
BF19 SubCBF19
BF33 SubCBF33
BF43 SubCBF43_Loop
BF47 SubCBF47
BF6E SubCBF6E_OnNonnegative
BF75 SubCBF75_OnZero
BF96 SubCBF96_Loop
BF97 SubCBF97_Loop
BF98 SubCBF98_OnCarrySet
BF9E SubCBF9E_Loop
BFC3 SubCBFC3
BFD2 SubCBFD2
BFE1 SubCBFE1_Loop
BFE2 SubCBFE2_Loop
BFF7 SubCBFF7
BFFC SubCBFFC
C003 SubCC003_Loop
C006 SubCC006
C016 SubCC016
C022 SubCC022_Loop
C023 SubCC023_Loop
C02E SubCC02E
C037 SubCC037
C039 SubCC039_OnNonzero
C041 SubCC041_Loop
C048 SubCC048_Loop
C054 SubCC054_Loop
C05E SubCC05E
C066 SubCC066_Loop
C071 SubCC071_Loop
C076 SubCC076
C088 SubCC088
C09A SubCC09A
C0AA SubCC0AA_OnNonzero
C0B1 SubCC0B1
C0C3 SubCC0C3
C0D5 SubCC0D5
C0E7 SubCC0E7
C0F1 SubCC0F1
C103 SubCC103_Loop
C106 SubCC106
C113 SubCC113
C125 SubCC125_Loop
C126 SubCC126
C12E SubCC12E_OnNonzero
C133 SubCC133
C140 SubCC140
C14D SubCC14D
C157 SubCC157
C161 SubCC161
C16D SubCC16D
C337 SubCC337
C355 SubCC355_OnNonnegative
C364 SubCC364_OnCarryClear
C36E SubCC36E_Loop
C38D SubCC38D_OnCarryClear
C3A1 SubCC3A1_OnCarryClear
C3B5 SubCC3B5_OnCarryClear
C3C2 SubCC3C2_OnNonnegative
C4F9 SubCC4F9
C4FB SubCC4FB_OnCarryClear
C543 SubCC543
C545 SubCC545_OnCarryClear
C557 SubCC557_Loop
C558 SubCC558
C561 SubCC561_OnNonnegative
C56F SubCC56F
C59E SubCC59E_OnCarryClear
C5AC SubCC5AC_Loop
C5CF SubCC5CF
C5F1 SubCC5F1_Loop
C5F3 SubCC5F3
C5FB SubCC5FB_Loop
C600 SubCC600_Loop
C619 SubCC619_Loop
C635 SubCC635_Loop
C63C SubCC63C_Loop
C654 SubCC654_Loop
C656 SubCC656_Loop
C65A SubCC65A_Loop
C75F SubCC75F
C76F SubCC76F_OnCarryClear
C778 SubCC778_Loop
C78E SubCC78E_Loop
C790 SubCC790_Loop
C794 SubCC794_Loop
C796 SubCC796_Loop
C7CD SubCC7CD_Loop
C7F8 SubCC7F8_Loop
C825 SubCC825_Loop
C82B SubCC82B
C845 SubCC845_Loop
C857 SubCC857_Loop
C859 SubCC859_Loop
C85A SubCC85A
C886 SubCC886_Loop
C893 SubCC893_OnZero
C899 SubCC899_Loop
C89A SubCC89A_Loop
C8A9 SubCC8A9_Loop
C8AE SubCC8AE
C8C2 SubCC8C2_OnCarryClear
C8C5 SubCC8C5_OnNonzero
C8CD SubCC8CD_Loop
C8D0 SubCC8D0_Loop
C8E3 SubCC8E3_Loop
C8EF SubCC8EF
C901 SubCC901_OnNonnegative
C9B2 SubCC9B2_OnNonzero
C9B8 SubCC9B8_OnZero
C9F4 SubCC9F4_OnNonnegative
C9FF SubCC9FF_OnNonnegative
CA15 SubCCA15
CA26 SubCCA26_OnNonzero
CA32 SubCCA32_Loop
CA38 SubCCA38
CA4B SubCCA4B_OnCarryClear
CA59 SubCCA59
CA5B SubCCA5B_OnNonzero
CA5D SubCCA5D_OnNonzero
CA5F SubCCA5F_OnNonzero
CB37 SubCCB37
CB48 SubCCB48_OnNonzero
CB4D SubCCB4D_Loop
CB62 SubCCB62_Loop
CB67 SubCCB67
CB70 SubCCB70_Loop
CB7E SubCCB7E_Loop
CBBC SubCCBBC
Reference in new issue View Git Blame Copy Permalink