http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46333
--- Comment #20 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-11-08 13:12:11 UTC --- There really is absolutely no point experimenting with this option anywhere other than on trunk. Maybe we should just disable it on 4.5 branch; it's a GCC-developer-only option at this point. *Many* problems with C++ compatibility have been fixed on trunk since 4.5 branched. See Joern's work on fixing problems building different targets with --enable-werror-always (many of the problems fixed are C++ compatibility warnings). No such fixes will be backported to 4.5 branch. Since we're now in development stage 3, I expect that the default build will not be C++ until after 4.6 branches, which means that C++ fixes will not be backported to 4.6 branch either once that branch is created. Bug reports and fixes for such issues are only useful for trunk, and they are only useful when each separate problem (each problem with a genuinely different cause) is reported as a separate well-defined bug report; omnibus issues mixing different problems are useless, although meta-bugs marked as depending on the individual C++-compatibility bugs can be useful. As it happens we have such a bug: bug 44433. So when you have a well-defined issue verified to exist on trunk and to be distinct from all existing bugs, only then file a separate bug for that issue and mark it as blocking bug 44433.
