From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
Subject: Re: Injecting trace code under GNAT
Date: Wed, 17 Jul 2013 10:00:38 +0200
Date: 2013-07-17T10:00:39+02:00 [thread overview]
Message-ID: <51e64f27$0$6569$9b4e6d93@newsspool3.arcor-online.net> (raw)
In-Reply-To: <07cb9baf-902c-4870-bfd1-aa8018e9d5c5@googlegroups.com>
On 17.07.13 09:33, wrostek wrote:
> Hi forum,
>
> I'm starting new to a fairly large GNAT project.
>
> Is the GNAT environment providing help to inject trace code
> on entry/exit of each subroutine?
>
> It doesn't matter if it is a one go over the whole codebase
> or by pre-processing prior to each compilation.
>
> I need to hook into my own routines to optimize things for
> perfomance reasons.
If it is about measuring relative performance of subprograms,
then one good approximation is kcachegrind.
(With compiler switch -fno-inline in particular).
If you can target the JVM using JGNAT, too, then this target
might allow injecting something.
The -fprofile* compiler switches might be interesting.
next prev parent reply other threads:[~2013-07-17 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 7:33 Injecting trace code under GNAT wrostek
2013-07-17 8:00 ` Georg Bauhaus [this message]
2013-07-17 8:40 ` wrostek
2013-07-17 8:15 ` Niklas Holsti
2013-07-17 23:38 ` Randy Brukardt
2013-07-18 6:03 ` J-P. Rosen
2013-07-23 6:59 ` wrostek
2013-07-23 13:43 ` Marc C
2013-07-23 15:44 ` wrostek
2013-07-24 9:10 ` wrostek
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox