===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.217
@@ -37,9 +37,7 @@
by Joachim Nadler and Tim Josling
<<a href="mailto:tej@melbpc.org.au">tej@melbpc.org.au</a>>.</li>
- <li><a href="http://www4.in.tum.de/~pizka/">GNU INSEL Compiler gic</a>.</li>
-
- <li><a href="http://www.codesourcery.com/public/cxx-abi/">
+ <li><a href="http://sourcery.mentor.com/public/cxx-abi/">
The V3 multi-vendor standard C++ ABI</a> is used in GCC releases 3.0 and
above.</li>
@@ -78,8 +76,6 @@
<br />Manufacturer: Various, by license from ARM
<br />CPUs include: ARM7 and ARM7T series (eg. ARM7TDMI), ARM9 and StrongARM
<br /><a href="http://infocenter.arm.com/help/index.jsp">ARM Documentation</a>
- <br /><a href="http://www.intel.com/design/intelxscale/273473.htm">Intel
- XScale Core Developer's Manual</a>
</li>
<li>AVR
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.2/c++-abi.html,v
retrieving revision 1.5
@@ -10,7 +10,7 @@
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://www.codesourcery.com/public/cxx-abi/">http://www.codesourcery.com/public/cxx-abi/</a>.
+ <a href="http://sourcery.mentor.com/public/cxx-abi/">http://sourcery.mentor.com/public/cxx-abi/</a>.
Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0
and GCC 3.1 releases.</p>
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.0/changes.html,v
retrieving revision 1.59
@@ -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://www.codesourcery.com/public/cxx-abi/">C++ ABI</a> for
+ href="http://sourcery.mentor.com/public/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