ReaperOfVeriod

0 Followers · 0 Following

• Joined on 2026-07-03

Repositories

9

Projects Packages Public Activity Starred Repositories

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:28:28 +00:00

d4aeb94616 Extent check inconclusive; the opcode field itself is not understood

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:27:06 +00:00

91b09955c8 The shortlist points at VU microcode; the decomp extents are unverified

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:23:51 +00:00

36d8d2b00c The frequency enrichment survives the redo; the disassembly does not

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:20:28 +00:00

4a826997f6 Redone on correct bytes: the disassembly chain is gone, 0x2ee138 is VU microcode

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:16:59 +00:00

cd1648571c The verified mapping is the flat memory image, not section indexing

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:14:16 +00:00

e6b3e0b091 Root cause: the per-section indexing used throughout this investigation was wrong

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 04:01:56 +00:00

f2d7e7ecd4 d97e7df was wrong: my section offset was wrong, not the decoder

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:56:01 +00:00

d97e7df41f Second decode error in the same investigation; stopping rather than trusting this decoder

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:47:30 +00:00

e1482abd75 Correct my own decode bug: there is a caller, and r2 is a return value

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:44:46 +00:00

349b498ddd r2 is never written in the enclosing function, and it has no callers

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:41:49 +00:00

eca1a16b17 Call sites: one caller, and it does not compute base + 0xc0

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:40:10 +00:00

cee17c95b1 Disassembled: 0xc0 is an address offset, and the walk is 16-byte strided

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:36:15 +00:00

05d9bf6cd7 The 72 concentrated candidates, and a float-constant ambiguity

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:34:44 +00:00

a2f8c924b4 moby_classes.offset enrichment is size-independent: 13x to 72x at matched size

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:32:36 +00:00

06531fb66c The 394 does not survive: 0xc0's rate rises with immediate-set size

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:30:09 +00:00

db1e69c0ab Ranking the 394 by size is backwards; record the confound

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:28:36 +00:00

3ea5ab799f moby_classes.offset is referenced by 394 functions; its neighbours by 1 to 14

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:23:15 +00:00

59957a02a2 Attribute the 0xc0 immediate sites to functions: 410 candidates

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:17:47 +00:00

56b00fb305 Fix the immediate scan by filtering on opcode; still no signal

ReaperOfVeriod pushed to main at ReaperOfVeriod/Going-Commando 2026-10-14 03:15:08 +00:00

27891ce5b4 Cross-reference scan by raw immediate: the method cannot tell