In case this is helpful: In November 2016, I got code coverage working on the vbccz compiler (much much smaller than GCC). But I was working on OSX, not Linux. I used Apple Clang's "--coverage" option plus the "gcov" tool. I believe this method still works on OSX as of December 2018.
As per above github link provided by you, Is it the code coverage of a file or vbccz compiler?
I have been trying to do the code coverage of gcc using the extended csmith.
BUILDING GCC: I tried building gcc-8.2 source code using
./src/configure --enable-languages=c,c++ --disable-bootstrap
--disable-multilib BOOT_CFLAGS="-O2 -g -ftest-coverage -fprofile-arcs"
I am compiling the program.c file (which is a random program
containing extension) as:
/path/to/xgcc -B path/to/stage1build/gcc -ftest-coverage program.c
The above command gives me code coverage of program .The problem is I
don't want to find code coverage of program.c using gcov and lcov.
I want to find code coverage of gcc's source code.
I tried searching on web but almost all of the answers tell me how do
I use gcov and lcov by giving example of a sample (.c) program .
As I had read it in your paper 'Finding And Understanding Bugs in C
Compiler' about the code coverage done for Csmith, Can you point out
the way you did the code coverage, any blogs written by you people or
some links in 'doing code coverage in gcc' ?