Update version numbering policy in the users guide

[ghc-hetmet.git] / docs / users_guide / sooner.xml

diff --git a/docs/users_guide/sooner.xml b/docs/users_guide/sooner.xml
index 1aba5d1..19c1c11 100644 (file)
--- a/docs/users_guide/sooner.xml
+++ b/docs/users_guide/sooner.xml
@@ -200,9 +200,6 @@ should go here!</para>
           mind-bogglingly clever.  Better to let GCC have a go, as it
           tries much harder on register allocation, etc.</para>
 
-         <para>At the moment, if you turn on <option>-O</option> you
-          get GCC instead.  This may change in the future.</para>
-
          <para>So, when we want very fast code, we use: <option>-O
          -fvia-C</option>.</para>
        </listitem>
@@ -509,18 +506,6 @@ f (Wibble x y)  # ugly, and proud of it
           <option>-A&lt;size&gt;</option><indexterm><primary>-A&lt;size&gt;
           RTS option</primary></indexterm> RTS options (see <xref
           linkend="rts-options-gc"/>).</para>
-
-         <para>This is especially important if your program uses a
-         lot of mutable arrays of pointers or mutable variables
-         (i.e. <literal>STArray</literal>,
-         <literal>IOArray</literal>, <literal>STRef</literal> and
-         <literal>IORef</literal>, but not <literal>UArray</literal>,
-         <literal>STUArray</literal> or <literal>IOUArray</literal>).
-         GHC's garbage collector currently scans these objects on
-         every collection, so your program won't benefit from
-         generational GC in the normal way if you use lots of
-         these.  Increasing the heap size to reduce the number of
-         collections will probably help.</para>
        </listitem>
       </varlistentry>
     </variablelist>