This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
profiling of contained procedures
- From: "Daniel Franke" <franke dot daniel at gmail dot com>
- To: fortran at gcc dot gnu dot org
- Date: Wed, 8 Nov 2006 17:15:50 +0100
- Subject: profiling of contained procedures
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=f4mpdctZHcvq+qYatTS7Exr4gkx8aINOpoIrXpvCD1BQfu8Ug0/YdBuMlq9x6MLfmgrJUCrKWT85DKmpWxkqqXZrSkWvofXQiwKnPrLl/fa8IAhP5aHQQpXUZ3BChCmJB8SCpJOu31Gq/ItIBeLJlk4ebcbdtplbumOUtlo6TjM=
Hi all,
profiling of contained procedures is next to impossible as they are
not seen by gprof (FCFLAGS="-g -pg -fno-inline"). The procedures in
question are listed within the binary as local symbols in text ("t")
by 'nm'. Problem: the profiler attributes the time spent in contained
procedures to the container. In my case, a single subroutine accounts
for 60% of the runtime - but I won't get any detailed information as
long as the contained procedures are hidden(?) from gprof/valgrind.
Is this behavior intentional?
Daniel