From:	combee AT cambridge DOT scr DOT slb DOT com (Leendert Combee)
Message-Id:	<9701201125.AA08187@cambridge.scr.slb.com>
Subject:	Re: profiling under djgpp
To:	djgpp AT delorie DOT com
Date:	Mon, 20 Jan 1997 11:25:02 +0000 (GMT)
In-Reply-To:	<5butdm$ckm@nntp.novia.net> from "Alaric Dailey" at Jan 20, 97 04:47:50 am
Mime-Version:	1.0

> 
> Eli Zaretskii (eliz AT is DOT elta DOT co DOT il) wrote:
> : 
> : On 16 Jan 1997, G.P. Tootell wrote:
> : 
> : > i can remove them? also can i profile parts of a function, ie. to refine the
> : > profile and hence determine which part of the routine is slowest (eg. i know
> : > routine_a() takes up too much time, can i set a breakpoint here to split the
> : > routine in two? or do i have to split it into 2 separate routines before it will 
> : > profile this way?)
> : 
> : AFAIK, gprof only supports file-level granularity, i.e. you can compile 
> : some files with -pg and others without it.  I don't think you can profile 
> : parts of a function.
> : 


  From "man gprof" under SunOS/UNIX I quote:

     A single function may be split into subfunctions for profil-
     ing by means of the MARK macro (see prof(3)).
 

  Unfortunately, I don't know yet how to use this macro nor whether it is supported by
  gcc/djgpp. However, it seems to do what you want....

  

- Raw text -