This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Multiple calls to __gcov_init

From: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Momchil Velikov <velco at fadata dot bg>, gcc at gcc dot gnu dot org
Date: Tue, 25 Apr 2006 09:39:20 -0700
Subject: Re: Multiple calls to __gcov_init
References: <444E1DE4.7040009@fadata.bg> <84fc9c000604250605g7345c220oa6587334db763fd4@mail.gmail.com>

On Tue, Apr 25, 2006 at 03:05:26PM +0200, Richard Guenther wrote:
> On 4/25/06, Momchil Velikov <velco@fadata.bg> wrote:
> >   Why does GCC emit multiple calls to __gcov_init, via mulitple (two) entries in
> > the ctors table? For example "int foo () { return 0; }" compiled with "gcc -S
> > -fprofile-generate" produces the following assembly file, where the ".ctors"
> > section conrtains two entries.
> 
> -funit-at-a-time fixes it.  But who uses -fprofile-generate with -O0
> these days...

gcov is used for coverage testing, and these are best run at -O0.

References:
- Multiple calls to __gcov_init
  - From: Momchil Velikov
- Re: Multiple calls to __gcov_init
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]