This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [doc patch] -lgcov
- From: Jan Hubicka <jh at suse dot cz>
- To: Nathan Sidwell <nathan at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sat, 19 Apr 2003 15:59:04 +0200
- Subject: Re: [doc patch] -lgcov
- References: <3EA1368B.9020908@codesourcery.com>
> Hi,
> I've installed this doc patch to clarify the linking requirements, and
> point out that concurrent updates DTRT (thanks to Jan's patch).
Thanks.
Perhaps we can also mention that threads and longjmps out of
asynchronous interrupts can not be profiled...
Honza
>
> nathan
> --
> Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
> The voices in my head said this was stupid too
> nathan at codesourcery dot com : http://www.cs.bris.ac.uk/~nathan/ : nathan at acm dot org
>
> 2003-04-19 Nathan Sidwell <nathan at codesourcery dot com>
>
> * doc/invoke.texi (-fprofile-arcs): Mention -lgcov, locking and
> fork behaviour.
>
> Index: doc/invoke.texi
> ===================================================================
> RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
> retrieving revision 1.268
> diff -c -3 -p -r1.268 invoke.texi
> *** doc/invoke.texi 17 Apr 2003 07:28:28 -0000 1.268
> --- doc/invoke.texi 19 Apr 2003 10:20:19 -0000
> *************** additional @option{-ftest-coverage} opti
> *** 3032,3042 ****
> every source file in a program.
>
> @item
> ! Link your object files as normal.
>
> @item
> Run the program on a representative workload to generate the arc profile
> ! information. This may be repeated any number of times.
>
> @item
> For profile-directed optimizations, compile the source files again with
> --- 3032,3047 ----
> every source file in a program.
>
> @item
> ! Link your object files with @option{-lgcov} or @option{-fprofile-arcs}
> ! (the latter implies the former).
>
> @item
> Run the program on a representative workload to generate the arc profile
> ! information. This may be repeated any number of times. You can run
> ! concurrent instances of your program, and provided that the file system
> ! supports locking, the data files will be correctly updated. Also
> ! @code{fork} calls are detected and correctly handled (double counting
> ! will not happen).
>
> @item
> For profile-directed optimizations, compile the source files again with