http://bugs.winehq.org/show_bug.cgi?id=14438
--- Comment #8 from Alexander Dorofeyev alexd4@inbox.lv 2008-08-21 11:03:12 --- (In reply to comment #6)
I forgot about the other issue with regression testing, namely wine not compiling.
as an example, this is what I got when trying to compile [d6bd8661ffeab62f003fb6cfee409fb593db8f74] dbghelp: Dwarf & parse context. (between 0.9.15 and 0.9.17).
/home/flat/install/git/wine-git/dlls/winex11.drv/palette.c:828: undefined reference to `GDI_GetObjPtr' /home/flat/install/git/wine-git/dlls/winex11.drv/palette.c:848: undefined reference to `GDI_ReleaseObj' ... /home/flat/install/git/wine-git/dlls/winex11.drv/palette.c:1267: undefined reference to `GDI_GetObjPtr' /home/flat/install/git/wine-git/dlls/winex11.drv/palette.c:1283: undefined reference to `GDI_ReleaseObj' collect2: ld returned 1 exit status winegcc: gcc failed.
As the other bug suggested that things changed between 0.9.15 and 0.9.16, I suspect I'll need to compile this to get it nailed down. Any ideas?
Oh, if the version that was ok is as old as 0.9.15 then it's a trouble indeed. It's very difficult to compile. Anyway, regression testing with 0.9.15 is pointless, as we already know what patch changed that, it was the ddraw rewrite. In the process of that rewrite some features that were considered hacky and unsafe were killed, unfortunately leading to performance degradation in some games. Now ddraw is totally different in implementation and wholly incompatible with that old code.
So it only makes sense to do a regression test if there were recent performance regressions (recent means something like 0.9.5x or later).