Field batch 4: deferred routines of batch 3 and the next field order #59
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Continue the field port after #56 (PR #57), same method and validation (draftc -> draft_check -> naming/restructuring -> portbridge -> groundtruth + shadow on the 5 routes US/JP, fuzz, instruction coverage, portstyle, debug/clang
-LE slow).Routines deferred by batch 3: MoveObjs, _c0714a, LoadLetterGfx, UpdateDlgWindow, UpdateSpotlights, CheckCollosions, TfrDlgTextGfx, TfrDlgCursorGfx, ClearDlgTextRegion (second DMA upload style), DrawTimer (divider, now compared by #58). Then the next routines of docs/coverage.md field order, up to about 30 routines. Frame-crossing routines are skipped (#37); every skip is listed with its reason. Original bugs found go to re/known-bugs.toml.
Merged in PR #62: 20 chapter 1 field routines. Shadow on the chapter 1 routes, 66 ports: US 1 866 252 calls, JP 1 694 094, 0 mismatch, 0 fallback; fuzz 0 mismatch; instructions US 1165/1205, JP 1021/1205; debug/clang ctest -LE slow 27/27. Skips listed in docs/ports.md.