PSO objdiff report
Episode I & II Plus · USA v1.02 · Treemap
Objects below are the current build splits. Source paths and object counts do not establish original TU boundaries or recovered game modules.
| Exact functions |
|---|
No entries in this view.
Report definitions and folding
Matched bytes are objdiff's exact-match counters. Linked bytes are selected from compiled source by the build; Ninja checks the output hash. A partly matched object retains its actual matched byte count.
A fold can combine several current objects. Rebuild the report to see the new ownership. Functions retain their original module/address identity when renamed or moved. Compare saved reports with tools/report_delta.py BEFORE AFTER --check to check exact functions and original data intervals, including linked coverage.
Inside an object, code rows are functions and data rows are sections. Their summed sizes can differ from the object counters because of padding. BSS describes zero-initialized storage. Function and object counts are not measures of recovered original TU boundaries.
Search and filters affect the table; the totals above it describe the selected module or object. Runtime asset verification is separate from these code/data counters.