http://bugs.winehq.org/show_bug.cgi?id=29168
--- Comment #189 from hash HASH.DuOrden@gmail.com 2012-03-13 14:42:36 CDT --- (In reply to comment #185)
The git-checkout from today compiled fine with gcc-4.6.2 and Carstens patch. I'm using Gentoo and only patched the ebuild - there are two Gentoo-specific patches applied also: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/wine/f... and http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-emulation/wine/f...
If it's not one of them, it's maybe the Gentoo-spec file for gcc.
Otherwise my point wasn't the ability to compile wine with newer ggc-versions, but the fix for the slowdown-problem without touching wine...
So you saying that you compiled otherwise stock, from Gentoo perspective view, WINE with gcc-4.6.2 and all works? Could you provide emerge --info please?
PS: And by the way, if you just want to add one patch to any packet in Gentoo you do not have to copy in to /usr/local/portage and alter it's .ebuild file, all you need to do is create directory in etc like this for wine: /etc/portage/patches/app-emulation/wine/ and place in it your patch, and next time emerge will compile it with your patch.