http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54112
Marc Glisse changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54112
--- Comment #4 from Marc Glisse 2012-08-13 11:55:04
UTC ---
Author: glisse
Date: Mon Aug 13 11:55:00 2012
New Revision: 190340
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190340
Log:
2012-08-13 Marc Glisse
PR libstdc++/54112
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54112
--- Comment #3 from Paolo Carlini 2012-07-28
10:50:15 UTC ---
Sure, sure. I'm still thinking that unless we have a regression, the less we do
for C++03 mode, the better. But if you can already see simple enough fixes for
both issues you are welco
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54112
--- Comment #2 from Marc Glisse 2012-07-28 10:26:42
UTC ---
(In reply to comment #1)
> Why it happens only in C++03 mode?
Because the complex.h wrapper distributed with libstdc++ does:
#ifdef __GXX_EXPERIMENTAL_CXX0X__
# include
#else
# if _GL
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54112
--- Comment #1 from Paolo Carlini 2012-07-28
10:11:04 UTC ---
Why it happens only in C++03 mode? I'm asking because if the issue isn't a
regression and we are sure that it doesn't happen in C++11 mode, I don't think
it can be considered high prio
