summaryrefslogtreecommitdiff
path: root/libstdc++-v3/docs/html/faq/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'libstdc++-v3/docs/html/faq/index.html')
-rw-r--r--libstdc++-v3/docs/html/faq/index.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/libstdc++-v3/docs/html/faq/index.html b/libstdc++-v3/docs/html/faq/index.html
index f472bfc9dc6..4d40397c60f 100644
--- a/libstdc++-v3/docs/html/faq/index.html
+++ b/libstdc++-v3/docs/html/faq/index.html
@@ -256,7 +256,7 @@ which is no longer available, thanks deja...-->
stuff" classes will probably migrate there.)
</p>
<p>For the bold and/or desperate, the
- <a href="http://gcc.gnu.org/fom_serv/cache/33.html">GCC FAQ</a>
+ <a href="http://gcc.gnu.org/extensions.html">GCC extensions page</a>
describes where to find the last libg++ source.
</p>
@@ -504,8 +504,8 @@ which is no longer available, thanks deja...-->
platforms. The assembly code accidentally used opcodes that are
only available on the i486 and later. So if you configured GCC
to target, for example, i386-linux, but actually used the programs
- on an i686, then you would encounter no problems. Only when
- actually running the code on a i386 will the problem appear.
+ on an i686, then you would encounter no problems. Only when
+ actually running the code on a i386 will the problem appear.
</p>
<p>This is fixed in 3.2.2.
</p>