see emu/testvectors/idxbug.6502

after all the loads/stores, memory looks something like: 0030: 70 71 72 00 00 ... ... 0070: C5 7C A1 00 00 ...

6502 Simulator (from internet) gives result A=0xA1 (specifically, after the AND instruction, A=0)

python emulator gives result A=0x5C (A=92) (specifically, after the AND instruction, A=0x93&0xC5)

I think this may be a problem with idy addressing as well