On Jun 20, 2012, at 4:18 AM, Luigia Ambrosio wrote:
Yes but it's not enough! I nedd the stack of the called methods and kernels. I just sent you my modified ex11 and the results of ./ex11 -log_summary <ex11.c> <log_summary> thanks again
gprof? Or the developer tools that Intel sells or Apple includes with XCode? Or Tau? Is that the kind of thing you are looking for. Apple's are fairly good for seeing the stack and where it spends time with the lines of source code etc. None of these is particular to PETSc but. Barry
Luigia Ambrosio
Il giorno 20/giu/2012, alle ore 10:45, Aron Ahmadia ha scritto:
Have you tried passing -log_summary to the command line?
A
On Wed, Jun 20, 2012 at 11:32 AM, Luigia Ambrosio <[email protected]> wrote: Hi all I'm interested in using PETSC with CUDA. I just downloaded and installed the developer version and I was testing the example #1 ($HOME/petsc-dev/src/vec/vec/examples/tutorials) to compute the norm of a vector. I would like to compare PETSC "without cuda" and "with cuda". Is there a way to profile a PETSC executable, obtain the stack of the called functions and methods and access to the function body? Can anybody make an exmple? Thanks a million