This is the mail archive of the
mailing list for the GCC project.
build time profiling?
- From: troy d.straszheim <troy at resophonic dot com>
- To: gcc at gcc dot gnu dot org
- Date: Sat, 7 Aug 2004 01:32:56 +0200
- Subject: build time profiling?
I'm new to the list. I'm working on a project now that is a real
rat's nest of templates and unnecessary (or mostly unnecessary)
#includes. As we start to try to disentangle things, it would be nice
to see where to put the effort... e.g. which header files take the
longest to compile, which get compiled most often. Generally a profile
of what has taken how much time over *multiple* gcc runs. Otherwise
one just greps a bit, sees which header files are included most often,
makes some guesses about which templates are most costly and often
used, that kind of thing. Not an optimal method.
This topic does not google well. "build time profiling" gets you a
bunch of stuff about gcov and -pg. The docs turn up nothing. I was
wondering if any thought had been given to this topic. I would be
willing to implement if such a thing was thought reasonable and