diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 58e008e6838..6eb5d1c4bf7 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,8 @@
+2003-02-01 Phil Edwards
For the bold and/or desperate, the - GCC FAQ + GCC extensions page describes where to find the last libg++ source.
@@ -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.This is fixed in 3.2.2.
diff --git a/libstdc++-v3/docs/html/faq/index.txt b/libstdc++-v3/docs/html/faq/index.txt index 3ea90597d43..c3e3452d5b1 100644 --- a/libstdc++-v3/docs/html/faq/index.txt +++ b/libstdc++-v3/docs/html/faq/index.txt @@ -177,8 +177,8 @@ and happened to be started by members of the Standards Committee. Certain "useful stuff" classes will probably migrate there.) - For the bold and/or desperate, the [61]GCC FAQ describes where to find - the last libg++ source. + For the bold and/or desperate, the [61]GCC extensions page describes + where to find the last libg++ source. _________________________________________________________________ 1.8 What if I have more questions? @@ -714,6 +714,31 @@ http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff headers whose directories are not searched directly, e.g.,