From octave-maintainers-request at bevo dot che dot wisc dot edu Wed Feb 18 13:42:17 2004
Subject: profiling (was: Re: Octave Compiler)
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Przemek Klosowski <przemek at jazz dot ncnr dot nist dot gov>
Cc: octave-maintainers at bevo dot che dot wisc dot edu
Date: Wed, 18 Feb 2004 13:41:26 -0600

On 18-Feb-2004, Przemek Klosowski <przemek at jazz dot ncnr dot nist dot gov> wrote:

| - good facilities for profiling (to find the weak/slow spots) and
|   debugging (NB, John, is there a way to instrument Octave to do a
|   high-level equivalent of gprof? Would that be a good idea? It
|   might simplify development work like fixing the concat slowness
|   that you did recently)

It would be possible to add some method of timing code to the
interpreter.  How fine-grained should the profile be?  Function calls
only or down to the individual statement level?  Should it only
profile the interpreted code or should it also time compiled code
(.oct files and built-in functions)?  At the level of compiled code,
you would only be able to get timings per function call unless you
actually compiled Octave for profiling and used the normal profiling
tools.  But from within Octave itself, we should be able to have some
profiling support.

jwe