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: How gcov handles untested files, prior and after GCC 3.4

From: Nathan Sidwell <nathan at codesourcery dot com>
To: Fredrik Johansson <frejo221 at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 09 Aug 2006 10:09:10 +0100
Subject: Re: How gcov handles untested files, prior and after GCC 3.4
References: <af9c5f440608010044u5ae6e633l537f223c44105587@mail.gmail.com> <44D3ADCF.3060708@codesourcery.com> <af9c5f440608090035s654608efpdf1c746a39315470@mail.gmail.com>

Fredrik Johansson wrote:

Nathan, if done properly do you think a patch (that again makes it
possible to extract the number of source lines in a untested lines)
would be accepted? And which way would be the most sutable: to make it
the standard behaviour to assume zero counts if no .gcda file are
found or to enable that feature via a flag?


I'm preparing a patch to
1) issue a warning
2) issue a notice in the output file
3) assume counts are zero

nathan

--
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

References:
- How gcov handles untested files, prior and after GCC 3.4
  - From: Fredrik Johansson
- Re: How gcov handles untested files, prior and after GCC 3.4
  - From: Nathan Sidwell
- Re: How gcov handles untested files, prior and after GCC 3.4
  - From: Fredrik Johansson

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