http://bugs.winehq.org/show_bug.cgi?id=12547
--- Comment #15 from Matthew Schultz mattsch@gmail.com 2008-07-28 11:33:52 --- (In reply to comment #14)
(In reply to comment #13)
What exactly was decided on that bug? I see a comment near the end that says they're adding -fomit-frame-pointer meaning that they're adding to an exclusion list of flags not to use or they found that it's not the problem?
Using -fomit-frame-pointer is the problem, I assure you because I had suffered it myself, using it breaks Wine protection schemes to the point that almost any protected app will not work even with a no-cd patch.
And the resolution of that bug report was to build Wine without -fomit-frame-pointer flag, because there is no point to aim for an imperceptible performace boost at the price of making a lot of apps unusable.
So they now (and I) make their Wine builds without -fomit-frame-pointer, and protected games started to work fine again.
(In reply to comment #14)
(In reply to comment #13)
What exactly was decided on that bug? I see a comment near the end that says they're adding -fomit-frame-pointer meaning that they're adding to an exclusion list of flags not to use or they found that it's not the problem?
Using -fomit-frame-pointer is the problem, I assure you because I had suffered it myself, using it breaks Wine protection schemes to the point that almost any protected app will not work even with a no-cd patch.
And the resolution of that bug report was to build Wine without -fomit-frame-pointer flag, because there is no point to aim for an imperceptible performace boost at the price of making a lot of apps unusable.
So they now (and I) make their Wine builds without -fomit-frame-pointer, and protected games started to work fine again.
This was a good guess as to what the problem is but I just checked it and gentoo strips all default CXXFLAGS on the wine ebuild and replaces it with -mcpu=athlon-xp -O3 -pipe. So -fomit-frame-pointer is not the issue here.