Rainer noticed that we were not consistent here for the GCC 4.7 release note, and after fixing those, I realized that GCC 4.6 is also affected.
Fixed thusly. Gerald Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.6/changes.html,v retrieving revision 1.139 diff -u -3 -p -r1.139 changes.html --- changes.html 1 Mar 2012 15:04:19 -0000 1.139 +++ changes.html 24 Mar 2012 22:03:02 -0000 @@ -369,7 +369,7 @@ declaration in the enclosing context, G++ now properly declares the name within the namespace of the function rather than the namespace which was open just before the function definition - (<a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43145">c++/43145</a>).</li> + (<a href="http://gcc.gnu.org/PR43145">c++/43145</a>).</li> <li>GCC now warns by default when casting integers to larger pointer types. These warnings can be disabled with the option @@ -379,7 +379,7 @@ <li>G++ no longer optimizes using the assumption that a value of enumeration type will fall within the range specified by the standard, since that assumption is easily violated with a conversion from integer - type (<a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43680">c++/43680</a>). + type (<a href="http://gcc.gnu.org/PR43680">c++/43680</a>). The old behavior can be restored with <code>-fstrict-enums</code>.</li> <li>The new <code>-fnothrow-opt</code> flag changes the semantics of @@ -415,7 +415,7 @@ place where a double-colon was intended.</li> <li>G++ no longer accepts <code>mutable</code> on reference members - (<a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33558">c++/33558</a>). + (<a href="http://gcc.gnu.org/PR33558">c++/33558</a>). Use <code>-fpermissive</code> to allow the old, non-conforming behaviour. </li>