http://bugs.winehq.org/show_bug.cgi?id=22890
--- Comment #9 from Richard shiningarcanine@gmail.com 2010-05-30 15:57:45 --- I took a closer look at what the WINE ebuild does on Gentoo Linux and it seems that it is not stripping -fomit-frame-pointer. While it appeared from the custom-cflags USE flag for the WINE ebuild that it ignored the system CFLAGS (like other ebuilds with custom-cflags USE flags do), the ebuild actually honors them. The custom-cflags USE flag is intended to enable users "Bypass strip-flags" as its very succinct documentation claims. Since -fomit-frame-pointer is not a strip flag for the ebuild, it is passed to the compiler from the system CFLAGS. I filed a bug report at the Gentoo Linux bug tracker to have this issue resolved:
http://bugs.gentoo.org/show_bug.cgi?id=322137
Earlier today I upgraded to WINE 1.2 RC 2 and confirmed that this issue is present in WINE 1.2 RC 2 as well, but unfortunately, that was before I realized that WINE was being built without frame pointers. I reinstalled WINE 1.2 RC 2 on my system with the following command:
CFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe" CPPFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe" CXXFLAGS="-O2 -march=prescott --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=2048 -pipe" emerge -1v wine
Doing that rebuilt it with frame-pointers and I can verify that the original issue I reported was not caused by the omission of frame pointers. The same issues that appeared in the stderr output from WINE 1.1.44 without frame pointers also appear in the stderr output from WINE 1.2 RC 2 with frame pointers. I can rebuild WINE 1.1.44 without frame pointers to verify that it is affected as well if necessary. I hope that this is satisfactory.