mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-09-19 19:07:48 +02:00
Henrik Rydgård
8a02d1ee0f
Three fixes, all of them things the new hardware tests turned up. sceMd5Block* and sceKernelUtilsMd5Block* shared one static md5_context and ignored the context pointer the caller passed in, with a TODO saying it would do "unless games do several MD5 concurrently". hash/md5ctx shows a real PSP keeps everything in the caller's 96 bytes and happily runs two digests at once, so do that instead: the state, the counters and the block buffer now live at ctxAddr in the game's own memory, in the layout the test pins down. Two interleaved digests come out right, and a context that gets copied mid-digest carries on correctly. As a side effect the state is now covered by savestates, which a file-static never was. MersenneTwister masked both halves with 0x80000000 where the low half needs 0x7FFFFFFF, so sceMt19937UInt and sceKernelUtilsMt19937UInt were returning a sequence that isn't MT19937 at all - every number differed from hardware from the first draw. hash/mt19937ctx computes the reference sequence itself and confirms the PSP is plain MT19937; with the mask fixed we match it for both seeds tested. Init also twists the array immediately, as hardware does, so a context that has been seeded but not drawn from now holds what a real one would. sceKernelCreateTlspl accepted partitions up to 9 before falling through to the permission check. Hardware draws the line at 6 - threads/tls/create records 7, 8, 9 and 10 all returning ILLEGAL_ARGUMENT - so 8 and 9 were coming back ILLEGAL_PERM. Note this is genuinely different from sceKernelCreateVpl right above it, which does let 8 and 9 through to ILLEGAL_PERM; the two had been sharing a check that was only ever right for Vpl. Risk worth naming: the MT19937 change alters the numbers any game gets from these calls. That's the point - they were wrong - but a savestate taken mid-sequence will resume with a generator that behaves differently from the one that made it.