Re: [Maxima-bugs] [ maxima-Bugs-572835 ] timer_info gives incorrect time

>>>>> ">" == noreply  <noreply@sourceforge.net> writes:

    >> Bugs item #572835, was opened at 2002-06-23 11:40
    >> You can respond by visiting: 
    >> http://sourceforge.net/tracker/?func=detail&atid=104933&aid=572835&group_id=4933

    >> Category: None
    >> Group: None
    >> Status: Open
    >> Resolution: None
    >> Priority: 5
    >> Submitted By: Nobody/Anonymous (nobody)
    >> Assigned to: Nobody/Anonymous (nobody)
    >> Summary: timer_info gives incorrect time

    >> Initial Comment:

    >> timer_info reports  times that are 10,000 times faster than thoser reported
    >> by showtime. An example:

    >> GCL (GNU Common Lisp)  Version(2.4.0) Fri Mar  1 22:06:12 CST 2002
    >> Licensed under GNU Library General Public License
    >> Contains Enhancements by W. Schelter
    >> Maxima 5.6 Fr[i Mar 1 22:05:34 CST 2002 (with enhancements by William Schelter).
    >> Licensed under the GNU Public License (see file COPYING)
    >> (C1) doodlebob(n) := block([z,x],
    >>         z : diff(x^x,x,n),
    >>         subst(1,x,z))$

    >> (C2) showtime : all;

    >> Evaluation took 0.00 seconds (0.00 elapsed)
    >> (D2) 				      ALL
    >> (C3) timer(doodlebob)$

This causes an error in CMUCL and Clisp.  There's a plain LAMBDA being
treated as a function that CMUCL and Clisp don't like.  Have to track
that down.

    >> In line (D4), we see that doodlebob(10) took 3.17 seconds while timer_info in 
    >> (D6) reports only 3.17e-4 seconds.  I think get('function, 'runtime) evaluates to 
    >> an integer in hundredths of seconds, but timer_info believes the unit of measure
    >> is microseconds.  To fix this, change (defined in mtrace.lisp)

I'll look into this and see what the appropriate value should be for
gcl and the other lisps.

Ray