3 ms·
I remember reading a writeup a few years ago from the guy who made BSNES, and him mentioning to get cycle exactness requires a crazy amount more CPU power than
by tombert 9y ago
I remember reading a writeup a few years ago from the guy who made BSNES, and him mentioning to get cycle exactness requires a crazy amount more CPU power than getting "cycle-good-enough-for-99%-of-things", and that he had to do some elaborate cooperative threading to get decent performance.
Has this been the case for you?
Also, 8088mph is super cool; great job on it!
- ajenner 9y agoMy current emulator is quite a lot slower than other 8088 emulators, but still quicker than real-time - it gets about 12.9MHz on a 2.67GHz Core i7 920. There are probably quite a few more things that could be done to optimize it. My "cooperative threading" consists of just having a "wait(n)" function which is called from the CPU Execution Unit emulator to emulate everything else for n cycles (i.e. the CPU Bus Interface Unit, the bus itself and everything else connected to it including the DMA controller and interrupt controller). That wait() function is the major bottleneck according to profiling, so if I modify it to do as little as possible (most of the time do very little other than increment a counter and compare to the top item in a priority queue) that would probably help a lot. Thanks!
- sp332 9y agoI remember that one, it's 3GHz for perfect emulation of a SNES which had a <25 MHz CPU. https://arstechnica.com/gaming/2011/08/accuracy-takes-power-one-mans-3ghz-quest-to-build-a-perfect-snes-emulator/ https://arstechnica.com/gaming/2011/08/accuracy-takes-power-...
- pvg 9y ago25 MHz is mentioned in the article as a basic requirement of the earliest SNES emulators. The SNES CPU itself clocks in at less than 4.