This is the mail archive of the gcc@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]

pch messages [was: Re: Suggestions for improving gcc 3.2 compilationspeed?]


On Mon, 10 Mar 2003, Mike Stump wrote:

> I think -v should say if a pch file is used, otherwise, it is hard to
> tell when the mechanism kicks in, well, unless you have a huge .h file
> and you know exactly how long it takes to parse, and mmap.  Wanna put a
> fprintf (stderr, "PCH file %s being used\n", name); in cpp_read_state?
> I think that will make it easy for the user to understand when PCH is
> used, and more importantly, to spot when it isn't being used.

JFYI: como prints such info too. E.g.

como  -I../include --pch --pch_dir /home/karel/arch/sl3/sl3/./pch
-DFAST_PCH -g  -a --long_long --implicit_extern_c_type_conversion
--diag_suppress=997     -c poa_base.cc -o poa_base.o

"poa_base.cc": using precompiled header file "/home/karel/arch/sl3/sl3/./pch/current.pch"
como  -I../include --pch --pch_dir /home/karel/arch/sl3/sl3/./pch
-DFAST_PCH -g  -a --long_long --implicit_extern_c_type_conversion
--diag_suppress=997     -c poa_impl.cc -o poa_impl.o

"poa_impl.cc": using precompiled header file "/home/karel/arch/sl3/sl3/./pch/os-unix.pch"
como  -I../include --pch --pch_dir /home/karel/arch/sl3/sl3/./pch
-DFAST_PCH -g  -a --long_long --implicit_extern_c_type_conversion
--diag_suppress=997     -c dynany.cc -o dynany.o

"dynany.cc": using precompiled header file "/home/karel/arch/sl3/sl3/./pch/current.pch"


Cheers,

Karel
--
Karel Gardas                  kgardas at objectsecurity dot com
ObjectSecurity Ltd.           http://www.objectsecurity.com


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