Date: Sun, 7 Nov 1999 16:53:36 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: infinity girl <entropic AT mpx DOT com DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: mcount, and gprof
In-Reply-To: <3822A1C4.73D19A86@mpx.com.au>
Message-ID: <Pine.SUN.3.91.991107165318.12805F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Fri, 5 Nov 1999, infinity girl wrote:

> unforunately i have deleted the version files in the manifest directory,
> but the version
> of the FAQ that i have says it was last updated fr djgpp version 2.01
> 
> so i think i have v2.01, unless the FAQ wasn't updated fr 2.02?

The FAQ wasn't updated since v2.01, so this doesn't prove anything.

To know what version of DJGPP you have installed, chdir to the DJGPP
lib subdirectory and then run the following command:

	strings libc.a | find "DJGPP libc built"

(This assumes DOS version of FIND!)

Now look for the string "DJGPP libc built".  It will be followed by a
date.  The library from v2.01 was built in October 1996; the one from
v2.02 was built in December 1998.

> but if those figures are supposed to be actual time, then there has to
> be something wrong.

Those figures should be very close to the actual run time of the
program.  Something is definitely wrong.

> i have a 486DX2/66 cpu, and just compiled the program with the -pg
> option (no debug info, or optimisations). 

That's not a good idea at all.  You should profile the optimized code,
since optimizations change the code dramatically.  If you profile a
non-optimized version, you might have a totally incorrect impression
about where to optimize.