X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fsooner.xml;h=19c1c11bdca877bec9aa5ab1948898ea03786685;hb=d4050431de1adddedb240e497f77f89301f77070;hp=1aba5d1af0afb4ffa66c489d98c93373f6875da2;hpb=0065d5ab628975892cea1ec7303f968c3338cbe1;p=ghc-hetmet.git
diff --git a/docs/users_guide/sooner.xml b/docs/users_guide/sooner.xml
index 1aba5d1..19c1c11 100644
--- a/docs/users_guide/sooner.xml
+++ b/docs/users_guide/sooner.xml
@@ -200,9 +200,6 @@ should go here!
mind-bogglingly clever. Better to let GCC have a go, as it
tries much harder on register allocation, etc.
- At the moment, if you turn on you
- get GCC instead. This may change in the future.
-
So, when we want very fast code, we use: .
@@ -509,18 +506,6 @@ f (Wibble x y) # ugly, and proud of it
-A<size>
RTS option RTS options (see ).
-
- This is especially important if your program uses a
- lot of mutable arrays of pointers or mutable variables
- (i.e. STArray,
- IOArray, STRef and
- IORef, but not UArray,
- STUArray or IOUArray).
- 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.