From 2769de23eefe3f5300ad034a01fd92a46895c6c5 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 17 Dec 2013 16:21:34 +0100 Subject: [PATCH] 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 --- gcc/ChangeLog | 4 ++++ gcc/doc/cfg.texi | 2 +- gcc/doc/passes.texi | 1 + 3 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 92d92762042..592bb8c4347 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,5 +1,9 @@ 2013-12-17 Thomas Schwinge + * 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 diff --git a/gcc/doc/cfg.texi b/gcc/doc/cfg.texi index b759e36ff75..1be3f47a792 100644 --- 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 3ed9a4fc204..9a68ad29c5c 100644 --- 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.