Closed omarandlorraine closed 1 year ago
Looks like the locus of the bug is line 826 of mos6502.cpp. But also, I don't know if C++ actually defines the order in which those reads happen. Can anyone shed any light on this?
Of course, if this is worth looking at, then also we could check if IRQ and NMI have the same issue.
Could you please fork the project and submit a pull request?
A real chip, and Mike Chambers' fake6502 as well, read the reset vector low byte first (i.e. $fffc) and then $fffd. But it seems like this emulator does it in reverse order.
I appreciate it's a tiny thing but it's showing as a difference in my test suite
What do we think? Do we care about such tiny differences?