documentation for profiling options

[Janis Johnson <janis at us dot ibm dot com>]

I've been experimenting with -fprofile-arcs and -fbranch-probabilities,
and along the way I started looking into the various GCC profiling
options.  The documentation for some of these is confusing so I'm
planning to update it.  I've got a few questions first, though.

 - The description of -a includes:  "This data could be analyzed by a
   program like tcov.  Note, however, that the format of the data is
   not what tcov expects.  Eventually GNU gprof should be extended to
   process this data."  This note has been in the documentation for a
   long time and it seems unlikely that either gcov or gprof will start
   handling this data.  Can the note be removed?

 - It appears that -ftest-coverage is useful only when used with
   -fprofile-arcs.  Is that true, or am I missing something?

 - Profiling options are in a section called "Options for Debugging
   Your Program and GCC."  This has:

      options for debugging your program
      -p, -pg, -a
      -Q, -ftime-report, -fmem-report
      -ax, -fprofile-arcs, -ftest-coverage
      options for debugging GCC

   Would it be OK to move -Q, -ftime-report and -fmem-report to after
   -test-coverage?  Then the user debugging options would be together,
   followed by the profiling options and then the options for
   debugging GCC.  I can see keeping them in place if they had an
   interesting change history, but they don't and they're very short.

How does gcc.1 get created?  I'd like to verify that changes I make to
doc/invoke.texi come through correctly for the man pages as well as
the html files.

Janis