Re: How gcov handles untested files, prior and after GCC 3.4

feature via a flag? Regards, Fredrik On 8/4/06, Nathan Sidwell <[EMAIL PROTECTED]> wrote: Fredrik Johansson wrote: > Why I ask is because I need to extract the number of lines even in > untested files, and I need it to work both on 3.3.6 and on various > 3.4.x versions. This u

Re: How gcov handles untested files, prior and after GCC 3.4

. The build system though needs to work in both environments. Regards, Fredrik On 8/4/06, Nathan Sidwell <[EMAIL PROTECTED]> wrote: Fredrik Johansson wrote: > Why I ask is because I need to extract the number of lines even in > untested files, and I need it to work both on 3.3.6 and o

How gcov handles untested files, prior and after GCC 3.4

.3.6 and on various 3.4.x versions. Thanks! Regards, Fredrik Johansson

Re: Gcov: Counting lines of source code (untested files) as gcov does

Apparently I forgot to CC this to the list last time, so here is a new attempt! Fredrik, if you can modify the source: if any line in a source file is touched, you'll get a .da file. So you could add a dummy routine to each file and call them all at startup. That will be an easier project than

Gcov: Counting lines of source code (untested files) as gcov does

ward with extracting the code from gcov.c? Thanks! Regards, Fredrik Johansson