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 <[email protected]> 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 [email protected] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah _______________________________________________ Gcl-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gcl-devel
