X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fsooner.xml;h=ea3e30609dc8f7155f09bad117e9545591ec0e01;hb=1bf40a4b38180b8b1c1bdaf4919bc327d5b27abe;hp=bb2eb871ec0e2d6c6f9484848839a4c2be36afa1;hpb=567954e31b359cf80ab67b8b100fe8488a859079;p=ghc-hetmet.git
diff --git a/docs/users_guide/sooner.xml b/docs/users_guide/sooner.xml
index bb2eb87..ea3e306 100644
--- a/docs/users_guide/sooner.xml
+++ b/docs/users_guide/sooner.xml
@@ -32,7 +32,7 @@ should go here!
garbage collection for GHC, which means less compilation
time. If you use the option,
you'll get a garbage-collector report. (Again, you can use
- the cheap-and-nasty
+ the cheap-and-nasty
option to send the GC stats straight to standard
error.)
@@ -152,14 +152,13 @@ should go here!
- Compile via C and crank up GCC:
+ Compile via LLVM:
- The native code-generator is designed to be quick, not
- mind-bogglingly clever. Better to let GCC have a go, as it
- tries much harder on register allocation, etc.
-
- So, when we want very fast code, we use: .
+ The LLVM code generator can sometimes do a far better job
+ at producing fast code then either the native code generator
+ or the C code generator. This is not universal and depends
+ on the code. Numeric heavy code seems to show the best
+ improvement when compiled via LLVM.
@@ -511,13 +510,13 @@ Use strip on your executables.
“I think I have a space leak…” Re-run your program
-with , and remove all doubt! (You'll
+with , and remove all doubt! (You'll
see the heap usage get bigger and bigger…)
[Hmmm…this might be even easier with the
RTS option; so… ./a.out +RTS
--Sstderr -G1...]
+-S -G1...]
-G RTS option
--Sstderr RTS option
+-S RTS option
@@ -539,7 +538,6 @@ be required).