http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51705
--- Comment #10 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-12-29 22:29:55 UTC --- On Thu, Dec 29, 2011 at 10:21:35PM +0000, chris at bubblescope dot net wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51705 > > --- Comment #8 from Chris Jefferson <chris at bubblescope dot net> 2011-12-29 > 22:21:35 UTC --- > (In reply to comment #4) > > On Thu, Dec 29, 2011 at 08:56:20PM +0000, chris at bubblescope dot net > > wrote: > > > Better take out C++03 support as well, seeing as there is no support for > > > the > > > 'export' keyword. > > > > > > But seriously, the C++11 support is as complete as any other compiler, > > > and in > > > common usage. Further, parts of libstdc++ need to be built in C++0x mode. > > > > > > > Please, re-read Ed's comment #2. g++ is telling the > > OS that "yes, I support C++11", when in fact it does > > not. For me, this means I can no longer work on > > gfortran until some work-around is in place to avoid > > this bug in g++. > > Please read my comment. I did. > You could make the same argument that using g++ should not report > as supporting C++03, as it does not support the 'export' keyword > and you could use this in headers. I have no qualms with this. If it does not support C++03, then should advertise that it does. > It is likely to be a very long time until g++ supports every > single corner case of C++11. Based on our experience with C++03, > it may never happen. If this is the case, then it definitely should not advertise that it does support C++11.
