libretroadmin e1f4bbf676 libretro: a same-instance state load keeps the compiled code it leaves ...

A state load reset every recompiler, so the frame after it compiled
the whole working set again; runahead loads a state every frame. A
state this session wrote now loads its code memory - EE RAM, IOP RAM,
the scratchpad and both VU micro memories - page by page: a page the
state changes is cleared of its compiled code the way a guest write to
it would be, then written, and a page it does not change keeps its
code. When what the recompilers build into code from outside memory
changes - the game-start and EELOAD hooks - they are reset as before,
and every other state still resets them.

tests/framepace's BIOS calls a routine in RAM that rewrites its own
add partway through the frames run, so every rollback in it goes back
across that rewrite; the run checks the rewrite falls inside it.
tests/savestate/loadorder checks the code is kept only through the
same-instance gate.

2026-11-01 17:54:42 +01:00

..

build.sh

One frame and that frame's audio per retro_run, nothing outside it

2026-10-08 20:10:39 +02:00

main.c

libretro: a same-instance state load keeps the compiled code it leaves

2026-11-01 17:54:42 +01:00