invoke.texi (Options for Debugging Your Program or GCC): Explain static numbering of dump files.

2010-11-24  Basile Starynkevitch  <basile@starynkevitch.net>

	* doc/invoke.texi (Options for Debugging Your Program or GCC):
	Explain static numbering of dump files.

From-SVN: r167114

gcc/ChangeLog

+2010-11-24  Basile Starynkevitch  <basile@starynkevitch.net>
+
+	* doc/invoke.texi (Options for Debugging Your Program or GCC):
+	Explain static numbering of dump files.
+
 2010-11-24  Joseph Myers  <joseph@codesourcery.com>
 
 	* common.opt (user_vect_verbosity_level): New Variable entry.

gcc/doc/invoke.texi

@@ -4968,11 +4968,15 @@ Says to make debugging dumps during compilation at times specified by
 @var{letters}.  This is used for debugging the RTL-based passes of the
 compiler.  The file names for most of the dumps are made by appending
 a pass number and a word to the @var{dumpname}, and the files are
-created in the directory of the output file.  @var{dumpname} is
-generated from the name of the output file, if explicitly specified
-and it is not an executable, otherwise it is the basename of the
-source file. These switches may have different effects when
-@option{-E} is used for preprocessing.
+created in the directory of the output file.  Note that the pass
+number is computed statically as passes get registered into the pass
+manager.  Thus the numbering is not related to the dynamic order of
+execution of passes.  In particular, a pass installed by a plugin
+could have a number over 200 even if it executed quite early.
+@var{dumpname} is generated from the name of the output file, if
+explicitly specified and it is not an executable, otherwise it is the
+basename of the source file. These switches may have different effects
+when @option{-E} is used for preprocessing.
 
 Debug dumps can be enabled with a @option{-fdump-rtl} switch or some
 @option{-d} option @var{letters}.  Here are the possible