This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Numbering of dump files in documentation
- From: Josef Zlomek <zlomj9am at artax dot karlin dot mff dot cuni dot cz>
- To: Kazu Hirata <kazu at cs dot umass dot edu>
- Cc: gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 4 Jul 2003 07:06:59 +0200
- Subject: Numbering of dump files in documentation
- References: <20030703145414.GA30605@artax.karlin.mff.cuni.cz> <20030703.120150.11611192.kazu@cs.umass.edu>
> > *************** Dump after running tracer, to @file{@var
> > *** 3215,3220 ****
> > --- 3215,3223 ----
> > @item u
> > @opindex du
> > Dump after null pointer elimination pass to @file{@var{file}.08.null}.
> > + @item V
> > + @opindex dV
> > + Dump after value range propagation, to @file{@var{file}.11.vrp}.
> > @item w
> > @opindex dw
> > Dump after the second flow pass, to @file{@var{file}.28.flow2}.
>
> Just a nit. You need to shift all the other passes after vrp by one.
>
> 28.flow2 -> 29.flow2, etc.
It would be better to remove the numbers from all -d? options in
documentation, as in description of -d? in passes.texi (see below)
so that we would not have to renumber the numbers when we add or remove a pass.
What others think about this?
+ @opindex dV
+ The option @option{-dV} causes a debugging dump of the RTL code after
+ this pass. This dump file's name is made by appending @samp{.vrp} to
+ the input file name.
+
@cindex global common subexpression elimination
@cindex constant propagation
@cindex copy propagation
Josef