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: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 29 Dec 2011 19:34:31 +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 #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-12-29 19:34:31 UTC ---
(In reply to comment #0)
> Essentially GCC is free to announce __cplusplus == 201103L for its experimental
> C++11 support, but the C++11 support should not be used during its own
> compilation step if it's not finished yet.
How should files needed for that C++11 support be compiled then?
It needs to be used to compile e.g. src/thread.cc which defines the functions
declared in the C++11 header <thread>
Until attributes are supported I think this should be dealt with by removing
[[noreturn]] using fixincludes.