===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.224
@@ -428,7 +428,7 @@
<p>For more details about the way that GCC implements these and other
C++ features, please read the <a
-href="http://mentorembedded.github.io/cxx-abi/">C++ ABI specification</a>.
+href="https://itanium-cxx-abi.github.io/cxx-abi/">C++ ABI specification</a>.
Note the <code>std::type_info</code> objects which <i>must</i> be
resolved all begin with "_ZTS". Refer to <code>ld</code>'s
documentation for a description of the "<code>-E</code>" &
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/c++-abi.html,v
retrieving revision 1.9
retrieving revision 1.11
@@ -9,10 +9,9 @@
<p>
The main point of the GCC 3.2 release is to have a relatively
stable and common C++ ABI for GNU/Linux and BSD usage, following
- the documentation at
- <a href="http://mentorembedded.github.io/cxx-abi/">http://mentorembedded.github.io/cxx-abi/</a>.
+ the Itanium C++ ABI.</p>
- Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
+ <p>Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
and GCC 3.1 releases.</p>
<p>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.69
@@ -182,7 +182,7 @@
<a href="#visibility"><code>-fvisibility</code> option</a>.</li>
<li>The compiler now uses the library interface specified by the <a
- href="http://mentorembedded.github.io/cxx-abi/">C++ ABI</a> for
+ href="https://itanium-cxx-abi.github.io/cxx-abi/">C++ ABI</a> for
thread-safe initialization of function-scope static variables.
Most users should leave this alone, but embedded programmers may
want to disable this by specifying