delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/03/19/10:07:13

From: Daniel <entropic AT mpx DOT com DOT au>
Newsgroups: comp.os.msdos.djgpp
Subject: mcount? [gprof question]
Date: Fri, 19 Mar 1999 21:55:16 +1000
Organization: Microplex PTY LTD
Lines: 24
Message-ID: <36F23B23.658E8FB3@mpx.com.au>
NNTP-Posting-Host: dialup-brisax5139.mpx.com.au
Mime-Version: 1.0
X-Trace: news1.mpx.com.au 921844374 8007 198.142.167.139 (19 Mar 1999 11:52:54 GMT)
X-Complaints-To: abuse AT mpx DOT com DOT au
NNTP-Posting-Date: 19 Mar 1999 11:52:54 GMT
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

hello everybody,


  i was using gprof for the first time today , and it had information
regarding a function.. mcount.  also, this function was given an index
number using (), rather than [].  it certainly isn't a function that i
called.. issit called by the libc routines?

  anyway apart from that mystery, gprof really helped!  it showed me how
stupid i was in writing a program that called feof() hundreds of
thousands of times, when i could keep track of that using the return
value of the I/O functions.. silly me!
  i ended up cutting the run-time in half, after realising that i had
stupidly used a linear searching method.  so yeah, all in all gprof is a
great utility.

just curious,
thanks,
daniel :)

PS:  oh one other thing.. my program spends over 40% of its time in
__dpmi_int.
     do the stdio functions use software interrupts??  [my program is
I/O heavy]

- Raw text -


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