--- Comment #14 from t7 at gmail dot com 2009-09-21 11:05 ---
I can confirm this is fixed in gcc-4_4-branch.
Thank you.
--
t7 at gmail dot com changed:
What|Removed |Added
--- Comment #13 from t7 at gmail dot com 2009-09-18 09:11 ---
Hmm I haven't noticed this bug has been fixed a week ago, since [Revision
151627], it was still reproducible at [Revision 151584] which was just a day
before.
Thanks!!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41
--- Comment #12 from mmitchel at gcc dot gnu dot org 2009-09-01 13:54
---
I think the question is whether the use of __optimize__ is in a standard Qt
release. If it is, then I'm quite concerned; it's bad if GCC 4.4.2 can't build
Qt/KDE.
(TBH, I'm concerned anyhow; if __optimize__ is u
--- Comment #11 from jakub at gcc dot gnu dot org 2009-09-01 09:32 ---
Mark, I don't think this should be P1, __optimize__ attribute is new in 4.4 (so
considering it regression is already quite weird, though the attribute is
ignored in older releases, so technically it is a regression, a
--- Comment #10 from hjl dot tools at gmail dot com 2009-09-01 00:35
---
Target optimization has many issues. See PR 37565.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41153
--- Comment #9 from jakub at gcc dot gnu dot org 2009-08-31 14:32 ---
The problem is that the optimization saving/restoring infrastructure seems to
ignore OVERRIDE_OPTIONS. i386 OPTIMIZATION_OPTIONS sets flag_pcc_struct_return
to 2 and expects OVERRIDE_OPTIONS to set it to 0 resp. 1 if
--- Comment #8 from rguenth at gcc dot gnu dot org 2009-08-31 12:45 ---
Confirmed.
class QString { };
QString fixString(QString string);
static QString fixPathToLocalOS(const QString &in)
{
return fixString(in);
}
void __attribute__((__optimize__ ("0")))
