3 ms·
In defense of the coffin, I'd say this is not so much about a bug, but about reverse engineering real world effects of undefined behavior (as caused by a bug in
by masswerk 7y ago
In defense of the coffin, I'd say this is not so much about a bug, but about reverse engineering real world effects of undefined behavior (as caused by a bug in software).
- deleted 7y ago[deleted]
- aidenn0 7y agoIf the goal of mgba is to reproduce the GBA hardware faithfully, then this is a pure software bug in mgba.
- NieDzejkob 7y agoYou are trying to argue about the meaning of the words being used. This is not productive, as what matters is what the author of the argument meant when they used that word.
- aidenn0 7y agoI don't think that's the case. When talking about emulation and virtualization and such, it is easy to get terms backwards. For example, a bug in the implementation of a virtualized device looks like a hardware bug to the client and like a software bug to the host.
- masswerk 7y agoTo be honest, I think it's about crossing the lines of emulation and simulation. In emulation, we mostly consider instruction level behavior as good enough, but here, we'll have to venture below cycle level and integrated hardware effects to copy the behavior.
- pingyong 7y agoThat is not the goal of mGBA (or any GBA emulator for that matter), btw. If you wanted to reproduce it faithfully, the emulator would be unusably slow. https://emulation.gametechwiki.com/index.php/Emulation_Accuracy https://emulation.gametechwiki.com/index.php/Emulation_Accur...
- aidenn0 7y agos/faithfully/faithfully enough/ Prior to the bug being fixed this was clearly not faithfully enough for at least 2 games.