From:	quacci AT vera DOT com (jon)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Any tips on optimizing C code?
Date:	Fri, 16 May 1997 15:41:21 GMT
Organization:	Yale University
Lines:	25
Message-ID:	<337c7efb.7433556@news.cis.yale.edu>
References:	<Pine DOT 3 DOT 89 DOT 9705130948 DOT B2877-0100000 AT alpha DOT hcst DOT com>
NNTP-Posting-Host:	slip-ppp-node-02.cs.yale.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

On Tue, 13 May 1997 13:42:21 GMT, Bryan Murphy <bryan AT hcst DOT com> wrote:

>Have you profiled your code with gprof yet?  That will give you the 
>biggest insights.  Optimizing is too big a topic and too dependant on
>your own coding style.  If you run gprof, it'll let you know where the
>slow parts of your program are.  Knowing what it is you have to 
>optimize is the first most important step, then just look for short
>cuts or other ways around things.

Thanks very much for the tip, and to the many other helpful replies in
this thread. 

I didn't even know I had gprof on my computer- but I do. Now, how do I
use it? running 

gprof example.exe

produces, in brief, a "gmon.out not found." Don't know what gmon.out
is/was.

Anyway, I looked a bit on DJ's site, no find yet. will look some more.
Any quick tips as to how to run it and how to study what it gives
back?

- Raw text -