This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51705] Build infrastructure should not use -std=c++0x until g++ properly supports it
- From: "chris at bubblescope dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 29 Dec 2011 22:21:35 +0000
- Subject: [Bug libstdc++/51705] Build infrastructure should not use -std=c++0x until g++ properly supports it
- Auto-submitted: auto-generated
- References: <bug-51705-4@http.gcc.gnu.org/bugzilla/>
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.
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.
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.