1 2002-08-14 Nathan Sidwell <nathan@codesourcery.com>
3 * doc/invoke.texi (-a): Remove documentation.
4 (-fprofile-arcs): Remove reference to -a, -ax options.
5 * doc/gcov.texi (Gcov Data Files): Data might be merged.
7 --- gcc/doc/gcov.texi.jj 2001-11-15 11:38:19.000000000 +0100
8 +++ gcc/doc/gcov.texi 2002-08-22 11:48:48.000000000 +0200
9 @@ -388,7 +388,7 @@ built with the GCC @option{-fprofile-arc
10 separate @file{.da} file is created for each source file compiled with
11 this option, and the name of the @file{.da} file is stored as an
12 absolute pathname in the resulting object file. This path name is
13 -derived from the source file name by substituting a @file{.da} suffix.
14 +derived from the object file name by substituting a @file{.da} suffix.
16 The format of the @file{.da} file is fairly simple. The first 8-byte
17 number is the number of counts in the file, followed by the counts
18 --- gcc/doc/invoke.texi.jj 2002-08-08 17:55:08.000000000 +0200
19 +++ gcc/doc/invoke.texi 2002-08-22 11:46:49.000000000 +0200
20 @@ -2831,20 +2831,6 @@ analysis program @code{gprof}. You must
21 the source files you want data about, and you must also use it when
27 -Generate extra code to write profile information for basic blocks, which will
28 -record the number of times each basic block is executed, the basic block start
29 -address, and the function name containing the basic block. If @option{-g} is
30 -used, the line number and filename of the start of the basic block will also be
31 -recorded. If not overridden by the machine description, the default action is
32 -to append to the text file @file{bb.out}.
34 -This data could be analyzed by a program like @code{tcov}. Note,
35 -however, that the format of the data is not what @code{tcov} expects.
36 -Eventually GNU @code{gprof} should be extended to process this data.
40 Makes the compiler print out each function name as it is compiled, and
41 @@ -2877,18 +2863,7 @@ optimization and code generation options
42 Control Optimization}).
44 The other use of @option{-fprofile-arcs} is for use with @code{gcov},
45 -when it is used with the @option{-ftest-coverage} option. GCC
46 -supports two methods of determining code coverage: the options that
47 -support @code{gcov}, and options @option{-a} and @option{-ax}, which
48 -write information to text files. The options that support @code{gcov}
49 -do not need to instrument every arc in the program, so a program compiled
50 -with them runs faster than a program compiled with @option{-a}, which
51 -adds instrumentation code to every basic block in the program. The
52 -tradeoff: since @code{gcov} does not have execution counts for all
53 -branches, it must start with the execution counts for the instrumented
54 -branches, and then iterate over the program flow graph until the entire
55 -graph has been solved. Hence, @code{gcov} runs a little more slowly than
56 -a program which uses information from @option{-a} and @option{-ax}.
57 +when it is used with the @option{-ftest-coverage} option.
59 With @option{-fprofile-arcs}, for each function of your program GCC
60 creates a program flow graph, then finds a spanning tree for the graph.
61 @@ -2898,11 +2873,6 @@ executed. When an arc is the only exit
62 instrumentation code can be added to the block; otherwise, a new basic
63 block must be created to hold the instrumentation code.
65 -This option makes it possible to estimate branch probabilities and to
66 -calculate basic block execution counts. In general, basic block
67 -execution counts as provided by @option{-a} do not give enough
68 -information to estimate all branch probabilities.
72 @opindex ftest-coverage