Date: Thu, 13 Jan 2000 09:44:02 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: David Cleaver <davidis AT ou DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: Question on a profiled program...
In-Reply-To: <387D337D.AE51B3A9@ou.edu>
Message-ID: <Pine.SUN.3.91.1000113094344.9693Y-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Jan 2000, David Cleaver wrote:

> My program is very integer math intensive, so thank you for the reply. 
> I now understand better what is going on.

Caveat: __umoddi3 is only relevant for operations on "long long" data
type (64-bit integers).  Do you have such variables in your program,
and if so, do they participate in the intensive part of your code?

In any case, no function should ever take 100% percent of the CPU
time.  If that's what the profile says, you are looking at a known bug
in DJGPP v2.02; upgrade to v2.03.