That is really a great tool.
It shows even how is the assembler mapped to the source code.
I was surprised when I learned that 90% of time spent in my function
goes to a result assignment stalling the processor.
the usual
function f : TStructure
var
b: TStructure;
begin
... some processing on b ...
f := b;
end;
Jan
On Jul 20, 2005, at 04:04, Jonas Maebe wrote:
On 05 Jul 2005, at 06:36, Jan Ruzicka wrote:
Was the profiling tested under OS X?
No, but I would urge you to use Shark from CHUD
(http://developer.apple.com/tools/performance/overview.html)
It's much better and versatile than gprof, and only requires regular
debugging information to work.
Jonas
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
