http://bugs.winehq.org/show_bug.cgi?id=22387
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2010-04-20 03:11:25 --- (In reply to comment #7)
Dmitry, I vividly remember bug 2488 which was indeed a wine's problem, rather than GCC's one, so I posted this bug thinking that there's a subtle bug in Wine's code.
Of course it's very nice that you remember a bug you reported 6 years ago.
However it's pretty strange that you have filed bug 22377 and bug 22385 which have been resolved as invalid with direct link to the gcc bug, and then you report this bug 22387. Marcus in the Comment #1 clearly said once again what's the source of the problem, and even after that your memory can't recognize some "vaguely similar" symptom of the problem?
If you tell me to refrain from posting GCC related bugs I'll do so.
Just a suggestion though, if you prefer for some reason to use your own custom compilation flags (although it's been stated many times that it's not recommended) with a bleeding edge gcc, then you could at least take some efforts to investigate the problem on your own, not dump it on somebody else's shoulders right away.