public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ed at 80386 dot nl" <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 23:55:00 -0000 [thread overview]
Message-ID: <bug-51705-4-No8Xvbix3C@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 #14 from Ed Schouten <ed at 80386 dot nl> 2011-12-29 23:30:19 UTC ---
(In reply to comment #13)
> Feel free to keep
> arguing otherwise, but wherever the problem lies, it's not that libstdc++ uses
> C++11 features
Steve and I merely have our doubts about the current value of __cplusplus
during the compilation of libstdc++ -- not whether C++11 features are used
inside libstdc++.
But this discussion starts to turn into an infinite loop. Doesn't Bugzilla
allow a bug reporter to unsubscribe? I trust you folks will get it sorted out
eventually.
next prev parent reply other threads:[~2011-12-29 23:31 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
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 [this message]
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-No8Xvbix3C@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: link
Be 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).