4 ms·
This is very cool, how does it count the ticks? It seems to just go instruction by instruction, but some instructions take multiple CPU ticks. Since this only s
by DSMan195276 4y ago
This is very cool, how does it count the ticks? It seems to just go instruction by instruction, but some instructions take multiple CPU ticks. Since this only seems to cover the CPU state for the moment I'm not sure it actually makes a difference though.
- toast0 4y agoLooking at the instructions, this test doesn't seem to care about timing. I've seen NES emulator test roms with prints for state after each instruction where they did include the number of cycles. When I was writing my (poor) NES emulator, I ran my code on the test rom and would stop if it hit an instruction I didn't handle or if the states didn't match. Pretty soon I had a fairly accurate CPU emulator.