This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Source code coverage of gcc
- From: Andi Kleen <ak at linux dot intel dot com>
- To: sameeran joshi <gsocsameeran at gmail dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 06 Dec 2018 16:00:06 -0800
- Subject: Re: Source code coverage of gcc
- References: <CAKz4L0HDyPjhtQyqHi-Erprmr2X9zuUo=oggczB8DN_EK9gAeA@mail.gmail.com>
sameeran joshi <gsocsameeran@gmail.com> writes:
> Hi,
> I have a random C program as a test case, for which I need to do
> source code coverage on gcc.
> I have used the gcov tool and further the lcov tool. The percentage of
> source code coverage which I get after using gcov, Is that the final %
> which I need to do gcc source code coverage?
>
> What does it mean to build gcc with -pg option, how does that help in
> source code coverage?
lcov/gcov can only work if the code is instrumented.
So this requires building gcc with BOOT_CFLAGS="-O2 -g -pg"
(see the chapter on building gcc in the manual for more information)
You would then run the instrumented gcc, which writes coverage
data to disk. Then lcov can be used to get a summary of coverage.
-Andi