> If it's something that depends on the order of static initialisation across files, > then really it's a legitimate bug that needs to be fixed. But I don't quite > understand the issue as you described, the text meandered, so I'm not sure what > you're saying.
For H@P, one of the rows of things to shoot was missing in the game Carnival, using a self-compile on Linux of the 0.177 tag of MAME. He then checked builds circa 0.152, and the bug wasn't there. Upon digging further, he found a number of affected games, not just Carnival or vicdual-driver games.
He traced the regression to something to do with how rgb_t is initialized when const, but then when attempting to reproduce the bug before digging deeper on a Windows machine, he found that the bug didn't happen on Windows.
He wonders, then, if this is an actual code issue with MAME, or if it's an issue with gcc, and if it is, whether or not it's platform-specific.
|