[PATCH] remove mention of -a and -ax in invoke.texi for 3.2

[Janis Johnson]

The message http://gcc.gnu.org/ml/gcc/2002-10/msg01615.html reported
that the 3.2 documentation references the -a and -ax options.  The
documentation for those options was removed, but they were still
mentioned in the entry for -profile-arcs.

OK for the 3.2 branch?  This text is already gone in the mainline.

2002-10-28  Janis Johnson  <janis187@us.ibm.com>

	* doc/invoke.texi (-profile-arcs): Remove references to -a and -ax.

Index: doc/invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.119.2.12.4.7
diff -u -r1.119.2.12.4.7 invoke.texi
--- doc/invoke.texi	23 Oct 2002 13:38:28 -0000	1.119.2.12.4.7
+++ doc/invoke.texi	28 Oct 2002 19:23:23 -0000
@@ -2933,18 +2933,7 @@
 Control Optimization}).
 
 The other use of @option{-fprofile-arcs} is for use with @code{gcov},
-when it is used with the @option{-ftest-coverage} option.  GCC
-supports two methods of determining code coverage: the options that
-support @code{gcov}, and options @option{-a} and @option{-ax}, which
-write information to text files.  The options that support @code{gcov}
-do not need to instrument every arc in the program, so a program compiled
-with them runs faster than a program compiled with @option{-a}, which
-adds instrumentation code to every basic block in the program.  The
-tradeoff: since @code{gcov} does not have execution counts for all
-branches, it must start with the execution counts for the instrumented
-branches, and then iterate over the program flow graph until the entire
-graph has been solved.  Hence, @code{gcov} runs a little more slowly than
-a program which uses information from @option{-a} and @option{-ax}.
+when it is used with the @option{-ftest-coverage} option.
 
 With @option{-fprofile-arcs}, for each function of your program GCC
 creates a program flow graph, then finds a spanning tree for the graph.
@@ -2953,11 +2942,6 @@
 executed.  When an arc is the only exit or only entrance to a block, the
 instrumentation code can be added to the block; otherwise, a new basic
 block must be created to hold the instrumentation code.
-
-This option makes it possible to estimate branch probabilities and to
-calculate basic block execution counts.  In general, basic block
-execution counts as provided by @option{-a} do not give enough
-information to estimate all branch probabilities.
 
 @need 2000
 @item -ftest-coverage