On Fri, 2009-06-12 at 22:31 -0400, Eli Zaretskii wrote: > > Date: Thu, 11 Jun 2009 22:27:48 -0400 > > From: Mike Shal <[email protected]> > > Cc: [email protected] > > > > Is there a better way to benchmark it to figure out the bottlenecks? > > One way would be to compile and link Make with -pg, invoke Make as you > always do in this project, and then run gprof on the resulting profile > data. Feel free to share the results here.
You can also use valgrind (if you're running on Linux anyway). I've used it for memory examination but I'm pretty sure there's a profiling tool available for it as well. The trick with both of these is that if you have a recursive make you'll have to figure out a way to combine the results; I don't think either of them have that ability natively, which is too bad. Maybe someone's already done this. If you have a non-recursive build environment it's significantly simpler of course. -- ------------------------------------------------------------------------------- Paul D. Smith <[email protected]> Find some GNU make tips at: http://www.gnu.org http://make.mad-scientist.us "Please remain calm...I may be mad, but I am a professional." --Mad Scientist _______________________________________________ Help-make mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-make
