[pooma-dev] Profiling POOMA: How to?

[James Crotinger]

> -----Original Message-----
> From: Gabriel Dos Reis [mailto:gdr at codesourcery.com]
> Sent: Thursday, August 16, 2001 6:48 PM
> To: pooma-dev at pooma.codesourcery.com
> Subject: [pooma-dev] Profiling POOMA: How to?
> 
> 
> 
> 		     Profiling POOMA (with gprof)
> 		       compiled with KCC or GCC
> 
>    This is a short note to let you get started with profiling POOMA
> compiled with KCC or GCC using gprof as a profiler.  That proceeds in
> three steps: 
> 
>     (i) Setting architecture dependent compiler options
>    (ii) Compiling the POOMA library, benchmarks and running them
>   (iii) Producing profiling information.
> 
> Note that both the library and the program being tested have to be
> compiled with profiling on, or else you won't have profiling
> information about the parts not compiled with profiling on.  Normally
> setting correctly options in the configuration file once should be
> OK. 
> 
> I) Setting architecture dependent compiler options
> 
>   To specify profiling options, you need to modify the architecture
> configuration file to be used to build POOMA. 
> 
> If you're using KCC then you have to modify 
> config/arch/<plateform>KCC.conf

We should probably add a -gprof option to configure to have it make these
additions itself. That way you'd be guaranteed that the entire "suite" would
be consistent. 

> [ At this point I suspect it would be much flexible to specify the
>   target specific profiling option at configure level instead of
>   modifying config/arch/<suite>.conf ]

Right.

> III) Producing profiling information.
> 
>   To produce the actual profiling information, you have to invoke
> gprof and the program being profiled as its argument.  Since gprof
> writes directly on the standard output, you might want to use a
> redirection :
> 
>    gprof atest > atest-pooma.prof

When I do this on my linux box (with ABCTest), gprof goes away for a very
long time and then core dumps (after printing a message about not being able
to allocate several gigabytes of memory). Any ideas? Is this related to your
caveat? 

  Jim
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sourcerytools.com/pipermail/pooma-dev/attachments/20010821/e4429e19/attachment.html>