Message-Id: <199609060127.SAA27316@bluesky.com>
Comments: Authenticated sender is <kbaca AT bluesky DOT skygames DOT com>
From: "Kevin Baca" <kbaca AT skygames DOT com>
To: djgpp AT delorie DOT com
Date: Thu, 5 Sep 1996 18:30:23 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Profiling

> > Hi, I was wondering if there was a profiling utility for DJGPP (v2)
> > available.
> 
> gprof... :)
>  
> > I want to be able to find out where my C program is spending most of its
> > time. (On my hard disk isn't really the answer I want!)
> 
> All you have to do is compile your program with -pg, then run it as
> usual,
> and then run gprof. AFAIK, this is in the FAQ!!!! (although I can't
> remember
> what section... ;)
> 
> One thing about gprof I have noticed though, if your subroutine or
> whatever
> takes less than 0.0555... seconds to execute, gprof claims it takes no
> time
> whatsoever to execute. As it is now, I have a program that takes about
> 1/5 of
> a second to run, calling several routines several hundred times, and
> none of
> them take any time! :)
> 
> Leathal.

I have a series of routines that reads the Machine Specific Registers 
on Pentium machines.  These registers provide profiling info down to 
a single cycle.  If anyone is interested, I can post or mail the 
source.  It's not very big.

-Kevin