This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: testing GCC
On Tue, 2004-02-24 at 19:55, Jane chen wrote:
> By now, I did not run the testsuite yet. But I've got
> 48.77% covered for genrtl.c.
The "make bootstrap" command causes gcc to be built 3 times. The first
time it is built by the compiler in the path. The second and third
times it builds itself. This allows us to perform a consistency check
to make sure the compiler is working before it is installed.
Since the instrumented compiler is building itself, it will generate
profile data when this happens.
Also, the "make bootstrap" command causes various libraries to be built,
and profile data will be generated when the libraries are built.
If you want to ignore this profile data, you can delete the .da (.gcda)
files before running the testsuite.
> I modified the Makefile because only by adding
> --enable-coverage no .bb file generated. Therefore
> gcov cannot be used.
This is because gcc-2.95 is old, and does not support the
--enable-coverage configure option. This configure option just gets
silently ignored. You need gcc-3.3 or later for this to work. Hence
for gcc-2.95 you have to modify the Makefile.
Setting CC is probably wrong. This only gets used for the first
compiler build. It will not be used for the second or third compiler
builds. I think you want to put the options in ALL_CFLAGS instead,
which is what gcc-3.3 does.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com