This is the mail archive of the
mailing list for the GCC project.
Re: How gcov handles untested files, prior and after GCC 3.4
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Fredrik Johansson <frejo221 at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 1 Aug 2006 13:07:13 -0700
- Subject: Re: How gcov handles untested files, prior and after GCC 3.4
- References: <firstname.lastname@example.org>
On Tue, Aug 01, 2006 at 09:44:56AM +0200, Fredrik Johansson wrote:
> [ gcov on a source file with no .da/.gcda file ]
> The 3.3.6 version assumes that the file not has been run (which is the
> correct behaviour in my book) whereas the 3.4.4 version just "gives
> up". I know that a large remake was done to gcov and it's .bb,.bbg,.da
> contra .gcno, gcda files when 3.4 came along, but is that the reason
> to change this beviour or has this been change due to some other fact?
It does seem that the old behavior is more useful, so one could argue
that this is a regression. It should be easy enough for a motivated
volunteer to fix, so we have the old behavior (assume all counts are zero
if we have a .gcno but no .gcda file) again. Alternatively, a flag
could be given to specify that missing .gcda file means all-counts-zero
and that gcov should shut up about the issue.