Date: Sun, 19 Jan 1997 09:29:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "G.P. Tootell" <gpt20 AT thor DOT cam DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: profiling under djgpp
In-Reply-To: <5bloof$k5d@lyra.csx.cam.ac.uk>
Message-ID: <Pine.SUN.3.91.970119092700.22250D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


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.

> dj_movedata or something similar takes up some considerable time too. again i
> don't know what's causing this to be able to rectify the problem :(

If you move a lot of data to and from the screen, that would involve 
dj_movedata.