Quote:
Originally Posted by jotd
going to adapt that to validate Musashi emulator.
|
I did the same when I switched from Musashi to my own CPU implementation in vAmiga. What I found out is that Musashi has cycle-counting issues with instructions that consume a variable number of cycles depending on the operands (like DIV).
Nevertheless, Musashi is a great core. What I really like about it is the very high code quality (which was one of the main reasons why I chose this core when I started vAmiga). However, at some point I had to switch to my own CPU implementation because Musashi doesn't keep track of when the CPU accesses memory (in Musashi, the clock is only incremented after a single instruction has been executed). This information is essential to accurately emulate bus sharing on the Amiga. It might not as important for other projects though.