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.
