This is the mail archive of the gcc-bugs@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: testing GCC


On Wed, 2004-02-25 at 21:43, Jane chen wrote:
> useful. There are no ALL_FLAGS in the Makefile I'm
> working on and I tried to put the coverage option in

You are looking at the toplevel Makefile, which is used to build gcc and
everything else.  Try looking at gcc/Makefile instead, which has
ALL_CFLAGS.

See also more recent gcc sources, and look at the COVERAGE_FLAGS support

>"flags to pass down to all sub_makes"). However, there
>are totally 106 *.bb files generated. And there are
>totally 139 *.c files existed.

Some files are only used for some targets, and hence not every .c file
will be compiled for your target.  A better check would be to compare
the number of .bb files against the number of .o files.

Some files are generator programs.  They get compiled by the build
compiler, and then generate a .c file that gets linked into cc1.  The
generator files do not need to be compiled with profile info, as they
will not be part of the compiler.  This may account for some of the
difference in the counts.

I believe that files that contain only data, no code, won't get .bb
files created for them, but I am not sure about this, and there are
probably no such files in the gcc sources anyways.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com


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