> Ok, can you be more specific why and how would this algorithm fail: - "Our algorithm > is simply that the disassembler outputs (prints to file) code for each instruction > instead of executing it."
Because if your ROM binary consists of something along these lines:
you will almost certainly lose "code sync" during the string at 0xA and end up disassembling incorrectly when you get back to code at 817.
> I find your response, and that of BIOS-D, quite odd, you two reacted as if I > criticized MAME, which I did not. I need you for this, I can not possibly do it by > myself. I would not be asking you questions if I did not think you can help me find > the answers. Is that ok, are we cool?
Well, your implication was that you'd discovered some amazing way to make games emulate faster that MAMEdev hadn't. Meanwhile we do use DRC, which gives equivalent run-time performance to static recompilation while avoiding the code/data problem entirely. So I'm still fuzzy on why this is even a thing.
Index 
Flat 
Re: Emulator: Interpreter vs. Compiler?
Reply
Re: It's called "static recompiler"
