Re: Loop profiling
- From: Chrisitan Christmann <plfriko@xxxxxxxx>
- Date: Wed, 28 Mar 2007 20:50:12 +0200
On Wed, 28 Mar 2007 16:43:34 +0000, Randy Howard wrote:
Any ideas? Right now, I help myself out with C macros but the
instrumentation is still very tedious.
Well, easy answer would be to write the loop iteration count statistics
to a log file, in a well-defined format that included the function
name, a line number, etc., then have another tool (or even
a shell script using grep intelligently) to pull the data back out and
present it in a more nicely formatted way.
Thank you for your ideas. But, as I understood your ideas, they all
expect the user to add some individual code for each loop under test.
That's what I'm currently doing, but for more complex applications
this becomes a tedious job. This was the reason why I was looking for
an automatic approach, something in the direction of gcov...
.
- Follow-Ups:
- Re: Loop profiling
- From: user923005
- Re: Loop profiling
- From: Martin Eisenberg
- Re: Loop profiling
- From: Randy Howard
- Re: Loop profiling
- References:
- Loop profiling
- From: Christian Christmann
- Re: Loop profiling
- From: Ed Prochak
- Re: Loop profiling
- From: Christian Christmann
- Re: Loop profiling
- From: Randy Howard
- Re: Loop profiling
- From: Christian Christmann
- Re: Loop profiling
- From: Randy Howard
- Loop profiling
- Prev by Date: implementation note for scapegoat tree
- Next by Date: Re: C++ Tutorial (a beginner's)
- Previous by thread: Re: Loop profiling
- Next by thread: Re: Loop profiling
- Index(es):
Relevant Pages
|