public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/51705] FreeBSD uses unsupported C++11 features when __cplusplus == 201103L Date: Thu, 29 Dec 2011 22:40:00 -0000 [thread overview] Message-ID: <bug-51705-4-67LmWxb7UG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51705-4@http.gcc.gnu.org/bugzilla/> 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.
next prev parent reply other threads:[~2011-12-29 22:30 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-29 19:34 [Bug libstdc++/51705] New: Build infrastructure should not use -std=c++0x until g++ properly supports it ed at 80386 dot nl 2011-12-29 19:42 ` [Bug libstdc++/51705] " redi at gcc dot gnu.org 2011-12-29 19:56 ` ed at 80386 dot nl 2011-12-29 21:13 ` chris at bubblescope dot net 2011-12-29 21:40 ` sgk at troutmask dot apl.washington.edu 2011-12-29 21:45 ` redi at gcc dot gnu.org 2011-12-29 22:07 ` ed at 80386 dot nl 2011-12-29 22:16 ` sgk at troutmask dot apl.washington.edu 2011-12-29 22:27 ` chris at bubblescope dot net 2011-12-29 22:30 ` [Bug bootstrap/51705] FreeBSD uses unsupported C++11 features when __cplusplus == 201103L redi at gcc dot gnu.org 2011-12-29 22:40 ` sgk at troutmask dot apl.washington.edu [this message] 2011-12-29 23:06 ` ed at 80386 dot nl 2011-12-29 23:13 ` sgk at troutmask dot apl.washington.edu 2011-12-29 23:31 ` redi at gcc dot gnu.org 2011-12-29 23:55 ` ed at 80386 dot nl 2011-12-30 0:12 ` sgk at troutmask dot apl.washington.edu 2011-12-30 4:02 ` kargl at gcc dot gnu.org 2011-12-30 6:08 ` sgk at troutmask dot apl.washington.edu 2011-12-30 10:47 ` andreast at gcc dot gnu.org 2011-12-30 10:49 ` ed at 80386 dot nl 2011-12-30 11:32 ` andreast at gcc dot gnu.org 2011-12-30 17:30 ` sgk at troutmask dot apl.washington.edu 2011-12-30 18:19 ` andreast at gcc dot gnu.org 2011-12-30 19:34 ` andreast at gcc dot gnu.org 2011-12-30 19:41 ` sgk at troutmask dot apl.washington.edu 2012-01-02 10:24 ` [Bug bootstrap/51705] [4.7 Regression] " rguenth at gcc dot gnu.org 2012-01-06 14:12 ` jason at gcc dot gnu.org 2012-01-06 15:10 ` bkorb at gnu dot org 2012-01-06 15:23 ` sgk at troutmask dot apl.washington.edu 2012-01-06 15:30 ` jakub at gcc dot gnu.org 2012-01-06 15:34 ` redi at gcc dot gnu.org 2012-01-06 15:59 ` andreast at gcc dot gnu.org 2012-01-06 16:11 ` bkorb at gnu dot org 2012-01-06 16:14 ` bkorb at gnu dot org 2012-01-06 16:15 ` sgk at troutmask dot apl.washington.edu 2012-01-09 20:13 ` sgk at troutmask dot apl.washington.edu 2012-01-09 20:33 ` andreast at gcc dot gnu.org 2012-01-09 21:34 ` sgk at troutmask dot apl.washington.edu 2012-01-09 21:47 ` chris at bubblescope dot net 2012-01-09 22:12 ` bkorb at gnu dot org 2012-01-09 22:31 ` sgk at troutmask dot apl.washington.edu 2012-01-09 22:37 ` ed at 80386 dot nl 2012-01-09 22:47 ` chris at bubblescope dot net 2012-01-09 22:50 ` ed at 80386 dot nl 2012-01-09 22:52 ` joseph at codesourcery dot com 2012-01-09 23:01 ` chris at bubblescope dot net 2012-01-10 13:46 ` jason at gcc dot gnu.org 2012-01-11 7:47 ` andreast at gcc dot gnu.org 2012-01-11 7:51 ` andreast at gcc dot gnu.org 2012-01-11 14:32 ` bkorb at gnu dot org 2012-01-11 16:24 ` sgk at troutmask dot apl.washington.edu 2012-01-11 18:36 ` andreast at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-51705-4-67LmWxb7UG@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).