[project @ 2002-08-29 12:57:34 by simonmar]

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

diff --git a/ghc/docs/users_guide/sooner.sgml b/ghc/docs/users_guide/sooner.sgml
index 75508a5..767de16 100644 (file)
--- a/ghc/docs/users_guide/sooner.sgml
+++ b/ghc/docs/users_guide/sooner.sgml
@@ -1,5 +1,5 @@
 <Chapter id="sooner-faster-quicker">
-<Title>Advice on: sooner, faster, smaller, stingier
+<Title>Advice on: sooner, faster, smaller, thriftier
 </Title>
 
 <Para>
@@ -128,7 +128,7 @@ individually with <Option>-fno-strictness</Option>.
 
 <Para>
 To figure out which part of the compiler is badly behaved, the
-<Option>-v2</Option><IndexTerm><option>-v</option></primary>
+<option>-v2</option><indexterm><primary><option>-v</option></primary>
 </indexterm> option is your friend.
 </Para>
 
@@ -230,7 +230,7 @@ register allocation, etc.</para>
 instead.  This may change in the future.</para>
 
 <Para>
-So, when we want very fast code, we use: <Option>-O -fvia-C -O2-for-C</Option>.
+So, when we want very fast code, we use: <Option>-O -fvia-C</Option>.
 </Para>
 </ListItem>
 </VarListEntry>
@@ -460,18 +460,19 @@ to compete with it, but link with it.
 </Para>
 
 <Para>
-<XRef LinkEnd="sec-ffi"> describes the foreign calling interface.
+<XRef LinkEnd="ffi"> describes the foreign function interface.
 </Para>
 </ListItem>
 </VarListEntry>
+
 <VarListEntry>
 <Term>Don't use <Literal>Float</Literal>s:</Term>
 <ListItem>
 <Para>
-We don't provide specialisations of Prelude functions for <Literal>Float</Literal>
-(but we do for <Literal>Double</Literal>).  If you end up executing overloaded
-code, you will lose on performance, perhaps badly.
-</Para>
+If you're using <literal>Complex</literal>, definitely use
+<literal>Complex Double</literal> rather than <literal>Complex
+Float</literal> (the former is specialised heavily, but the latter
+isn't).</para>
 
 <Para>
 <Literal>Floats</Literal> (probably 32-bits) are almost always a bad idea, anyway,
@@ -520,7 +521,7 @@ Decrease the &ldquo;go-for-it&rdquo; threshold for unfolding smallish
 expressions.  Give a
 <Option>-funfolding-use-threshold0</Option><IndexTerm><Primary>-funfolding-use-threshold0
 option</Primary></IndexTerm> option for the extreme case. (&ldquo;Only unfoldings with
-zero cost should proceed.&rdquo;)  Warning: except in certain specialiised
+zero cost should proceed.&rdquo;)  Warning: except in certain specialised
 cases (like Happy parsers) this is likely to actually
 <Emphasis>increase</Emphasis> the size of your program, because unfolding
 generally enables extra simplifying optimisations to be performed.
@@ -536,8 +537,8 @@ Use <Literal>strip</Literal> on your executables.
 
 </Sect1>
 
-<Sect1 id="stingier">
-<Title>Stingier: producing a program that gobbles less heap space
+<Sect1 id="thriftier">
+<Title>Thriftier: producing a program that gobbles less heap space
 </Title>
 
 <Para>