From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,ccd04b355056eb04
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: performance tuning with gnat
Date: 1996/05/10
Message-ID: <Dr7JB1.5Er@world.std.com>#1/1
X-Deja-AN: 154184309
references: <4mvkq1$nr4@cville-srv.wam.umd.edu> <4n069g$rrf@eri1.erinet.com>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-05-10T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <4n069g$rrf@eri1.erinet.com>,
James E. Hopper  <jhopper@erinet.com> wrote:
>In article <4mvkq1$nr4@cville-srv.wam.umd.edu> Eric Anthony Spear,
>spear@wam.umd.edu writes:
>>Hi!  I'm running gnat 3.01.  I have a program that runs slower than I'd
>>like.  The trouble is, I don't know which parts are causing the
>>slowdown.  Are there any tools that can help me profile my program,
>>breaking down by procedure/function cpu usage and/or disk usage/wait
>>times?

I had some luck with GNAT on Linux using gprof.  Use the -pg option to
the linker (that is, put "-largs -pg" on the gnatmake command line).
Then run gprof.  If you use -pg on the compiler, in addition to the
linker, it's supposed to give even more useful information.
Unfortunately, I got core dumps when I tried that, and I didn't
investigate further.

- Bob