This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: how to profile gfortran code?


> 
>     Can anyone describe the procedure for profiling gfortran code
> using the typical gnu devtools? While I could run Shark on MacOS X
> I was going to first try with the normal approach to profiling which
> subroutines in xplor-nih are most used in the gfortran build compared
> to the xlf build. Of course, on Darwin we don't have the option of
> using valgrind. Thanks in advance for any pointers on how to get
> started with this.

Shark is actually the best option here.  valdrind is not really a 
profiler.  The equivalent program to Shark is oprofile but that runs
only on GNU/Linux (and only on x86_64 and i686, there might be a port to
powerPC64 too).


-- Pinski


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]