public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/54324] [4.8 Regression] GCC install document does not list minimum required g++ version
Date: Wed, 12 Dec 2012 10:57:00 -0000 [thread overview]
Message-ID: <bug-54324-4-JNI6DVICJZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54324-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54324
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-12-12 10:56:40 UTC ---
(In reply to comment #7)
> Another proposed patch.
> http://gcc.gnu.org/ml/gcc-patches/2012-12/msg00766.html
I very strongly second what stevenb said:
GCC 3.2 claims many things, but any GCC that has the old C++ parser
has known non-conformances. IMHO we should only support GCC versions
with the "new" C++ parser, i.e. GCC 3.4 and up.
Expecting people to bootstap with GCC 3.2 to check it doesn't barf on some
perfectly valid piece of C++ is unreasonable. If people didn't bootstrap with
3.2 then incompatibilities would creep in and not be found, so claiming that
using 3.2 is possible would be a lie. Just say no.
next prev parent reply other threads:[~2012-12-12 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 18:20 [Bug other/54324] New: GCC install document does not list minimum required g++ versions gary at intrepid dot com
2012-08-20 7:19 ` [Bug other/54324] [4.8 Regression] GCC install document does not list minimum required g++ version rguenth at gcc dot gnu.org
2012-09-19 14:38 ` rguenth at gcc dot gnu.org
2012-11-16 1:07 ` pinskia at gcc dot gnu.org
2012-12-10 18:11 ` aldyh at gcc dot gnu.org
2012-12-10 19:40 ` aldyh at gcc dot gnu.org
2012-12-11 10:13 ` rguenth at gcc dot gnu.org
2012-12-11 10:20 ` rguenth at gcc dot gnu.org
2012-12-11 10:21 ` rguenth at gcc dot gnu.org
2012-12-12 5:09 ` aldyh at gcc dot gnu.org
2012-12-12 10:57 ` redi at gcc dot gnu.org [this message]
2012-12-18 15:21 ` aldyh at gcc dot gnu.org
2012-12-18 15:28 ` aldyh at gcc dot gnu.org
2012-12-18 16:22 ` aldyh 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-54324-4-JNI6DVICJZ@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).