X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fdebugging.vsgml;h=cdf951c9ccf168b257acd04862b5b3dae9845a1e;hp=23cd5ca0370ee13aa7b92213848312cab9eb509d;hb=438596897ebbe25a07e1c82085cfbc5bdb00f09e;hpb=967cc47f37cb93a5e2b6df7822c9a646f0428247

diff --git a/ghc/docs/users_guide/debugging.vsgml b/ghc/docs/users_guide/debugging.vsgml
index 23cd5ca..cdf951c 100644
--- a/ghc/docs/users_guide/debugging.vsgml
+++ b/ghc/docs/users_guide/debugging.vsgml
@@ -17,13 +17,13 @@ HACKER TERRITORY. HACKER TERRITORY.
 <nidx>GHC phases, changing</nidx>
 <nidx>phases, changing GHC</nidx>
 
-You may specify that a different program
-be used for one of the phases of the compilation system, in place of
-whatever the driver @ghc@ has wired into it.  For example, you
-might want to try a different assembler.  The
-@-pgm<phase-code><program-name>@<nidx>-pgm&lt;phase&gt;&lt;stuff&gt; option</nidx> option to
-@ghc@ will cause it to use @<program-name>@ for phase
-@<phase-code>@, where the codes to indicate the phases are:
+You may specify that a different program be used for one of the phases
+of the compilation system, in place of whatever the driver @ghc@ has
+wired into it.  For example, you might want to try a different
+assembler.  The
+@-pgm<phase-code><program-name>@<nidx>-pgm&lt;phase&gt;&lt;stuff&gt;
+option</nidx> option to @ghc@ will cause it to use @<program-name>@
+for phase @<phase-code>@, where the codes to indicate the phases are:
 
 <tabular ca="ll">
 <bf>code</bf> | <bf>phase</bf> @@
@@ -34,6 +34,7 @@ C    | Haskell compiler @@
 c    | C compiler@@
 a    | assembler @@
 l    | linker @@
+dep  | Makefile dependency generator @@
 </tabular>
 
 %----------------------------------------------------------------------
@@ -46,8 +47,9 @@ The preceding sections describe driver options that are mostly
 applicable to one particular phase.  You may also <em>force</em> a
 specific option @<option>@ to be passed to a particular phase
 @<phase-code>@ by feeding the driver the option
-@-opt<phase-code><option>@.<nidx>-opt&lt;phase&gt;&lt;stuff&gt; option</nidx> The
-codes to indicate the phases are the same as in the previous section.
+@-opt<phase-code><option>@.<nidx>-opt&lt;phase&gt;&lt;stuff&gt;
+option</nidx> The codes to indicate the phases are the same as in the
+previous section.
 
 So, for example, to force an @-Ewurble@ option to the assembler, you
 would tell the driver @-opta-Ewurble@ (the dash before the E is
@@ -84,24 +86,9 @@ example: @ghc -noC -ddump-simpl Foo.hs@
 
 <tag>@-hi@:</tag>
 <nidx>-hi option</nidx>
-<em>Do</em> generate an interface file (on @stdout@.) This would
-normally be used in conjunction with @-noC@, which turns off interface
-generation; thus: @-noC -hi@.
-
-<tag>@-hi-with-&lt;section&gt;@:</tag>
-<nidx>-hi-with option</nidx>
-Generate just the specified section of an interface file. In case you're
-only interested in a subset of what @-hi@ outputs, @-hi-with-&lt;section&gt;@
-is just the ticket. For instance 
-
-<tscreen> <verb>
--noC -hi-with-declarations -hi-with-exports
-</verb> </tscreen>
-
-will output the sections containing the exports and the
-declarations. Legal sections are: @declarations@, @exports@,
-@instances@, @instance_modules@, @usages@, @fixities@, and
-@interface@.
+<em>Do</em> generate an interface file.  This would normally be used in
+conjunction with @-noC@, which turns off interface generation;
+thus: @-noC -hi@.
 
 <tag>@-dshow-passes@:</tag>
 <nidx>-dshow-passes option</nidx>
@@ -159,6 +146,12 @@ really desperate:
 % ghc -noC -O -ddump-simpl -dverbose-simpl -dcore-lint Foo.hs
 </verb></tscreen>
 
+<tag>@-ddump-simpl-iterations@:</tag>
+<nidx>-ddump-simpl-iterations option</nidx>
+Show the output of each <em/iteration/ of the simplifier (each run of
+the simplifier has a maximum number of iterations, normally 4).  Used
+when even @-dverbose-simpl@ doesn't cut it.
+
 <tag>@-dppr-{user,debug,all@}:</tag>
 <nidx>-dppr-user option</nidx>
 <nidx>-dppr-debug option</nidx>