Document passes.def.

	gcc/
	* doc/cfg.texi (Control Flow): Refer to passes.def instead of
	passes.c.
	* doc/passes.texi (Pass manager): Refer to passes.def.

From-SVN: r206054

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 92d92762042585dbc22ed20c116c8ed153abed49..592bb8c434723245d056324983a5c2ac3567707c 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,9 @@
 2013-12-17  Thomas Schwinge  <thomas@codesourcery.com>
 
+       * doc/cfg.texi (Control Flow): Refer to passes.def instead of
+       passes.c.
+       * doc/passes.texi (Pass manager): Refer to passes.def.
+
        * doc/gccint.texi (Top): Fix inclusion order.
 
 2013-12-17  Kyrylo Tkachov  <kyrylo.tkachov@arm.com>

diff --git a/gcc/doc/cfg.texi b/gcc/doc/cfg.texi
index b759e36ff75260edd5f7c2eefbf32aeb94c105c4..1be3f47a7920b69e9cedce28bc3052f216eb64f0 100644 (file)
--- a/gcc/doc/cfg.texi
+++ b/gcc/doc/cfg.texi
@@ -23,7 +23,7 @@ used to represent the control flow graph are defined in
 
 In GCC, the representation of control flow is maintained throughout
 the compilation process, from constructing the CFG early in 
-@code{pass_build_cfg} to @code{pass_free_cfg} (see @file{passes.c}).
+@code{pass_build_cfg} to @code{pass_free_cfg} (see @file{passes.def}).
 The CFG takes various different modes and may undergo extensive
 manipulations, but the graph is always valid between its construction
 and its release.  This way, transfer of information such as data flow,

diff --git a/gcc/doc/passes.texi b/gcc/doc/passes.texi
index 3ed9a4fc20462a8cc5276c6fe3e4b2137eb9367b..9a68ad29c5c0620e99fddf8bcbeb335717ee57da 100644 (file)
--- a/gcc/doc/passes.texi
+++ b/gcc/doc/passes.texi
@@ -208,6 +208,7 @@ semantic checks), it should return @code{GS_ERROR}.
 
 The pass manager is located in @file{passes.c}, @file{tree-optimize.c}
 and @file{tree-pass.h}.
+It processes passes as described in @file{passes.def}.
 Its job is to run all of the individual passes in the correct order,
 and take care of standard bookkeeping that applies to every pass.