[project @ 2000-04-03 12:47:08 by simonmar]

don't mention non-existent RTS options.

2 files changed, 27 insertions, 24 deletions

diff --git a/ghc/docs/users_guide/gone_wrong.sgml b/ghc/docs/users_guide/gone_wrong.sgml
index b5910c9960..9467460f49 100644
--- a/ghc/docs/users_guide/gone_wrong.sgml
+++ b/ghc/docs/users_guide/gone_wrong.sgml
@@ -315,7 +315,8 @@ exception (please report it if it does).
 
 <Para>
 Glasgow Haskell is a changing system so there are sure to be bugs in
-it.  Please report them to <Email>glasgow-haskell-bugs@haskell.org</Email>!  (However, please
+it.  Please report them to
+<Email>glasgow-haskell-bugs@haskell.org</Email>!  (However, please
 check the earlier part of this section to be sure it's not a known
 not-really-a problem.)
 </Para>
@@ -331,9 +332,9 @@ Don't omit them because &ldquo;Oh, they won't be interested&hellip;&rdquo;
 <ListItem>
 
 <Para>
- What kind of machine are you running on, and exactly what
-version of the operating system are you using? (<Command>uname -a</Command> or <Command>cat
-/etc/motd</Command> will show the desired information.)
+What kind of machine are you running on, and exactly what version of
+the operating system are you using? (<Command>uname -a</Command> or
+<Command>cat /etc/motd</Command> will show the desired information.)
 
 </Para>
 </ListItem>
@@ -373,8 +374,8 @@ have, etc.
 <ListItem>
 
 <Para>
- If practical, please send enough source files/interface files
-for us to duplicate the problem.
+ If practical, please send enough source files for us to duplicate the
+ problem.
 
 </Para>
 </ListItem>
@@ -434,9 +435,9 @@ it <Emphasis>probably is</Emphasis> a GC bug.
 <ListItem>
 
 <Para>
-If it crashes with the normal
-collector, but not when you force two-space collection (<Option>-F2s</Option>
-runtime flag), then it <Emphasis>probably is</Emphasis> a GC bug.
+If it crashes with the normal collector, but not when you force
+two-space collection (<Option>-G1</Option> runtime flag), then it
+<Emphasis>probably is</Emphasis> a GC bug.
 </Para>
 </ListItem>
 
@@ -445,9 +446,9 @@ runtime flag), then it <Emphasis>probably is</Emphasis> a GC bug.
 </Para>
 
 <Para>
-If it <Emphasis>is</Emphasis> a GC bug, you may be able to avoid it by using a
-particular heap size or by using a <Option>-F2s</Option> runtime flag.  (But don't
-forget to report the bug!!!)
+If it <Emphasis>is</Emphasis> a GC bug, you may be able to avoid it by
+using a particular heap size or by using a <Option>-G1</Option>
+runtime flag.  (But don't forget to report the bug!!!)
 </Para>
 
 <Para>
diff --git a/ghc/docs/users_guide/sooner.sgml b/ghc/docs/users_guide/sooner.sgml
index dd38339478..e7cae66420 100644
--- a/ghc/docs/users_guide/sooner.sgml
+++ b/ghc/docs/users_guide/sooner.sgml
@@ -120,11 +120,10 @@ to correct it.
 </Para>
 
 <Para>
-The parts of the compiler that seem most prone to wandering off for a
-long time are the abstract interpreters (strictness and update
-analysers).  You can turn these off individually with
-<Option>-fno-strictness</Option><IndexTerm><Primary>-fno-strictness anti-option</Primary></IndexTerm> and
-<Option>-fno-update-analysis</Option>.<IndexTerm><Primary>-fno-update-analysis anti-option</Primary></IndexTerm>
+The part of the compiler that is occasionally prone to wandering off
+for a long time is the strictness analyser.  You can turn this off
+individually with <Option>-fno-strictness</Option>.
+<IndexTerm><Primary>-fno-strictness anti-option</Primary></IndexTerm>
 </Para>
 
 <Para>
@@ -550,16 +549,19 @@ Use <Literal>strip</Literal> on your executables.
 </Para>
 
 <Para>
-&ldquo;I think I have a space leak&hellip;&rdquo;  Re-run your program with
-<Option>+RTS -Sstderr</Option>,<IndexTerm><Primary>-Sstderr RTS option</Primary></IndexTerm> and remove all doubt!
-(You'll see the heap usage get bigger and bigger&hellip;)  &lsqb;Hmmm&hellip;this
-might be even easier with the <Option>-F2s</Option><IndexTerm><Primary>-F2s RTS option</Primary></IndexTerm> RTS
-option; so&hellip; <Command>./a.out +RTS -Sstderr -F2s</Command>...]
+&ldquo;I think I have a space leak&hellip;&rdquo; Re-run your program
+with <Option>+RTS -Sstderr</Option>, and remove all doubt!  (You'll
+see the heap usage get bigger and bigger&hellip;)
+&lsqb;Hmmm&hellip;this might be even easier with the
+<Option>-G1</Option> RTS option; so&hellip; <Command>./a.out +RTS
+-Sstderr -G1</Command>...]
+<IndexTerm><Primary>-G RTS option</Primary></IndexTerm>
+<IndexTerm><Primary>-Sstderr RTS option</Primary></IndexTerm>
 </Para>
 
 <Para>
-Once again, the profiling facilities (<XRef LinkEnd="profiling">) are the basic tool for demystifying the space
-behaviour of your program.
+Once again, the profiling facilities (<XRef LinkEnd="profiling">) are
+the basic tool for demystifying the space behaviour of your program.
 </Para>
 
 <Para>