delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/01/11/05:47:07

Message-ID: <387A5447.B39CDAF4@ou.edu>
From: David Cleaver <davidis AT ou DOT edu>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Question on a profiled program...
Lines: 15
Date: Mon, 10 Jan 2000 15:51:03 -0600
NNTP-Posting-Host: 129.15.140.115
X-Complaints-To: usenet AT ou DOT edu
X-Trace: news.ou.edu 947540994 129.15.140.115 (Mon, 10 Jan 2000 15:49:54 CST)
NNTP-Posting-Date: Mon, 10 Jan 2000 15:49:54 CST
Organization: The University of Oklahoma
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

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.

-David C.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019