diff DOCS/users_against_developers.html @ 6583:4b7d097a9c69

big update

--- a/DOCS/users_against_developers.html	Thu Jun 27 23:48:53 2002 +0000
+++ b/DOCS/users_against_developers.html	Fri Jun 28 06:07:46 2002 +0000
@@ -63,6 +63,11 @@
 bugs</B>. If you do, you will only get banned from our mailing list because
 we have had more than enough flame wars over GCC 2.96. Please let the matter rest.</P>
 
+<P><B>gcc 3.0.4-RedHat update</B>: RedHat managed to break gcc again, this
+  time the victim is 3.0.4 . It may fail with internal compiler error when
+  compiling with GUI support. DO NOT REPORT THIS BUG TO US! Use 2.95.3 or
+  a vanilla 3.0.4 compiled from source.</P>
+
 <P>If you have problems with GCC 2.96, you can get 2.96-85 packages from the
 Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
 3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
@@ -102,11 +107,11 @@
 welcome to create binary packages as you see fit.</P>
 
 <P>Another impediment to binary redistribution was compiletime optimizations
-for CPU architecture.  <B>MPlayer</B> now supports runtime CPU detection.
-Although this implies a small speed sacrifice, it is now possible to create
-binaries that run on different members of the Intel CPU family. For optimum
-performance you may wish to disable runtime CPU detection before compilation
-(<CODE>configure --disable-runtime-cpudetection</CODE>).</P>
+for CPU architecture.  <B>MPlayer</B> now supports runtime CPU detection
+(specify the <CODE>--enable-runtime-cpudetection</CODE> option when
+compiling). It is disabled by default because it implies a small speed
+sacrifice, it is now possible to create binaries that run on different
+members of the Intel CPU family.</P>
 
 <P><A NAME=nvidia><B>nVidia</B></A></P>