Ian Lance Taylor wrote:
Yang Zhang <yanghatespam@xxxxxxxxx> writes:
Hi, are there any tools or hooks available that would help with
profiling compilation time within g++? I'd like to gain a better
understanding of where the time goes, primarily on two dimensions:
- Which files does the compiler spend most of its time working with?
- What stages of compilation are most expensive?
Use the -ftime-report option.
Ian
Neat! Is there something similar for breaking down the time into time
spent on individual files so that I can see which #included files are
the most costly? (If you treat the compiler as a template language
interpreter then you can even imagine getting call-graph profiling results.)
--
Yang Zhang
http://www.mit.edu/~y_z/