<tag>@-ddump-<pass>@:</tag>
<nidx>-ddump-<pass> options</nidx>
Make a debugging dump after pass @<pass>@ (may be common enough to
-need a short form...). Some of the most useful ones are:
+need a short form...). You can get all of these at once (<em/lots/ of
+output) by using @-ddump-all@, or most of them with @-ddump-most@.
+Some of the most useful ones are:
-<tabular ca="ll">
-@-ddump-rdr@ | reader output (earliest stuff in the compiler) @@
-@-ddump-rn@ | renamer output @@
-@-ddump-tc@ | typechecker output @@
-@-ddump-deriv@ | derived instances @@
-@-ddump-ds@ | desugarer output @@
-@-ddump-simpl@ | simplifer output (Core-to-Core passes) @@
-@-ddump-stranal@ | strictness analyser output @@
-@-ddump-usagesp@ | UsageSP inference pre-inf and output @@
-@-ddump-occur-anal@ | `occurrence analysis' output @@
-@-ddump-spec@ | dump specialisation info @@
-@-ddump-stg@ | output of STG-to-STG passes @@
-@-ddump-absC@ | <em>un</em>flattened Abstract~C @@
-@-ddump-flatC@ | <em>flattened</em> Abstract~C @@
-@-ddump-realC@ | same as what goes to the C compiler @@
-@-ddump-asm@ | assembly language from the native-code generator @@
-</tabular>
+<descrip>
+<tag>@-ddump-parsed@:</tag> oarser output
+<tag>@-ddump-rn@:</tag> renamer output
+<tag>@-ddump-tc@:</tag> typechecker output
+<tag>@-ddump-deriv@:</tag> derived instances
+<tag>@-ddump-ds@:</tag> desugarer output
+<tag>@-ddump-spec@:</tag> output of specialisation pass
+<tag>@-ddump-rules@:</tag> dumps all rewrite rules (including those generated by the specialisation pass)
+<tag>@-ddump-simpl@:</tag> simplifer output (Core-to-Core passes)
+<tag>@-ddump-usagesp@:</tag> UsageSP inference pre-inf and output
+<tag>@-ddump-cpranal@:</tag> CPR analyser output
+<tag>@-ddump-stranal@:</tag> strictness analyser output
+<tag>@-ddump-workwrap@:</tag> worker/wrapper split output
+<tag>@-ddump-occur-anal@:</tag> `occurrence analysis' output
+<tag>@-ddump-stg@:</tag> output of STG-to-STG passes
+<tag>@-ddump-absC@:</tag> <em>un</em>flattened Abstract~C
+<tag>@-ddump-flatC@:</tag> <em>flattened</em> Abstract~C
+<tag>@-ddump-realC@:</tag> same as what goes to the C compiler
+<tag>@-ddump-asm@:</tag> assembly language from the native-code generator
+</descrip>
-<nidx>-ddump-rdr option</nidx>%
+<nidx>-ddump-all option</nidx>%
+<nidx>-ddump-most option</nidx>%
+<nidx>-ddump-parsed option</nidx>%
<nidx>-ddump-rn option</nidx>%
<nidx>-ddump-tc option</nidx>%
<nidx>-ddump-deriv option</nidx>%
<nidx>-ddump-ds option</nidx>%
<nidx>-ddump-simpl option</nidx>%
+<nidx>-ddump-cpranal option</nidx>%
+<nidx>-ddump-workwrap option</nidx>%
+<nidx>-ddump-rules option</nidx>%
<nidx>-ddump-usagesp option</nidx>%
<nidx>-ddump-stranal option</nidx>%
<nidx>-ddump-occur-anal option</nidx>%
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>
+<tag>@-dppr-{user,debug@}:</tag>
<nidx>-dppr-user option</nidx>
<nidx>-dppr-debug option</nidx>
-<nidx>-dppr-all option</nidx>
Debugging output is in one of several ``styles.'' Take the printing
of types, for example. In the ``user'' style, the compiler's internal
ideas about types are presented in Haskell source-level syntax,
insofar as possible. In the ``debug'' style (which is the default for
-debugging output), the types are printed in the most-often-desired
-form, with explicit foralls, etc. In the ``show all'' style, very
-verbose information about the types (e.g., the Uniques on the
-individual type variables) is displayed.
+debugging output), the types are printed in with
+explicit foralls, and variables have their unique-id attached (so you
+can check for things that look the same but aren't).
+
+<tag>@-ddump-simpl-stats@:</tag>
+<nidx>-ddump-simpl-stats option</nidx>
+Dump statistics about how many of each kind
+of transformation too place. If you add @-dppr-debug@ you get more detailed information.
<tag>@-ddump-raw-asm@:</tag>
<nidx>-ddump-raw-asm option</nidx>
projects / ghc-hetmet.git / blobdiff