Re: profiling, what takes so long?

[Torsten Mohr]

Hi,

thank you all for your hints.

it seems my first mail was missing some information:

Yes, in the office we work on Win32.

I asked my question on this mailing list because i did not
think of using some external profiling tool.
I rather thought i'd add some calls in the sources of "make"
to measure the time within "make" directly.
I thought of summing up all the time used for different issues
and printing them afterwards.

Has anybody got some hints for this?
Would something like this generally make sense in "make"?
A report could look like this:

Time spent for 'stat()':
Time spent searching for files:
Time spent for external commands:

What else could make sense to measure?


Thanks for the hint of using Clearmake, but i'd rather stay
with GNU make.


Best regards,
Torsten.