dynarmic: drop the cached code page when a range is invalidated

MemoryReadCode keeps the last code page it read, and only an ISB, an IC
instruction or a full cache clear reset it. InvalidateCacheRange did not,
so blocks recompiled after a range was invalidated could still decode the
old instructions when that page was the cached one. The gdbstub hits this
on every breakpoint: inserting or removing one writes the instruction and
invalidates its range, so breakpoints were skipped, fired after removal,
or single steps ran from stale code.

0 files changed, 0 insertions, 0 deletions