Mail Archives: djgpp/1997/01/20/03:31:44
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.
:
: > 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.
Alaric B. Williams has something called libhw at his website that is
supposed to be able to time bits of code ( I don't know how well this
works I haven't used it yet ) also there is the "Zen Timer" from "The Zen
of Code Optimization" by Abrash wchi can be used to time specific bits of
code.
Scitech Software has a port of the "Zen Timer" for djgpp at
ftp://ftp.scitechsoft.com
And Then Alaric will have to tell you were to get his "libhw" I don't
remember where I got my copy.
These things should help supplement gprof for you!!
--
--Alaric Dailey (alaric AT novia DOT net) :->
####################################################
We go left, right, left, right, left-
They're left in the right again.
We go right, left, right, left, right-
We've no rights left anymore.
-Martin Walkyier (Skyclad)
- Raw text -