[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: Visit

From: Camm Maguire
Subject: [Gcl-devel] Re: Visit
Date: Thu, 06 Aug 2009 12:17:14 -0400
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

Greetings!  One other goal I'd like to achieve this go around is
profiling without having to have a separate slower gprof image handy.
This is now doable as all function calls can optionally be redirected
via the fast link mechanism to a statistics collecting procedure.  (Of
course, this would leave out low lying system profiling, such as GBC,
etc.)  I'm planning on leaving the gprof option, but providing this
new facility as a perhaps more convenient alternative.

Schelter had a direct interface to PROFIL, which produces a flat list
of functions with the time spend in each.  We have the potential to
also keep track of a call tree as gprof does, without gprof.  What do
you think of the gprof output?  What sort of profiling information is
most useful?  Are items like compiled size, fixnum conversion,
consing, data side effect calls (e.g. rplaca) useful reportables to
the end user?

Take care,

Robert Boyer <address@hidden> writes:

>> Separately, does Bob Boyer have a few extra cycles for some email
>> questions/consultation?  
> Most happy to share what little I know!
> Bob

Camm Maguire                                        address@hidden
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]