From:	eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Question on a profiled program...
Date:	11 Jan 2000 09:49:04 GMT
Organization:	Ericsson Erisoft AB, Sweden
Message-ID:	<85euag$6av$2@antares.lu.erisoft.se>
References:	<387A5447 DOT B39CDAF4 AT ou DOT edu>
NNTP-Posting-Host:	spica-144.lu.erisoft.se
X-Newsreader:	TIN [version 1.2 PL2]
Lines:	23
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

David Cleaver (davidis AT ou DOT edu) wrote:
: Hello everyone,

: I know that this was sort of addressed in the FAQ, but, my problem is a
: little bit different.  In the FAQ there was a question relating to one
: of the DJGPP libraries eating about 60% of the run time of the program. 
: The FAQ stated that it was either I/O or "real-mode services" that would
: produce this result.  I know I don't have much I/O (only 2 printf
: statements) so, what are these "real-mode services"?

: BTW, in the FAQ it was __dpmi_int that was being called extensively. 
: However, on my machine the "function" being called extensively is
: "__umoddi3".  Are these two related?  Does it matter which is being
: called extensively?  Thank you for any info you can provide.

No I don't think so. __umoddi3 sounds like unsigned modulus
operation. If your program is integer math intensive, I think this is
normal.


Right,

							MartinS

- Raw text -