From: Ramachandran Lakshmanan
Subject: CMUCL bug? get-internal-run-time
Date: Wed, 14 Jul 1999 00:00:00 +0000
Message-ID: <378CC9CF.64EECC6B@chemeng.ed.ac.uk>

My installed version of CMU CL (17f) appears to have a bug in
GET-INTERNAL-RUN-TIME.

This throws off all profiling.

(get-internal-run-time)

always returns

0

Anyone have a bug fix?

Thanks,

Rama

--
Cogito ergo computo                ...               Computo ergo sum
School of Chemical Engineering,   University of Edinburgh,   Scotland
http://www.chemeng.ed.ac.uk/people/rama           +44(131)650-4862(W)
ftp://ftp.chemeng.ed.ac.uk/pub2/rama/             +44(131)650-6551(F)

• Re: CMUCL bug? get-internal-run-time Tim Bradshaw
  • Re: CMUCL bug? get-internal-run-time Raymond Toy
• Re: CMUCL bug? get-internal-run-time Gareth McCaughan

From: Tim Bradshaw
Subject: Re: CMUCL bug? get-internal-run-time
Date: Thu, 15 Jul 1999 00:00:00 +0000
Message-ID: <ey34sj6wb0n.fsf@lostwithiel.tfeb.org>

* Ramachandran Lakshmanan wrote:
> My installed version of CMU CL (17f) appears to have a bug in
> GET-INTERNAL-RUN-TIME.

> This throws off all profiling.

> (get-internal-run-time)

This was a bug I remember in 17s.  It's fixed at least in 18a on
sparc.

--tim

From: Raymond Toy
Subject: Re: CMUCL bug? get-internal-run-time
Date: Thu, 15 Jul 1999 00:00:00 +0000
Message-ID: <4npv1u9htm.fsf@rtp.ericsson.se>

>>>>> "Tim" == Tim Bradshaw <···@tfeb.org> writes:

    Tim> * Ramachandran Lakshmanan wrote:
    >> My installed version of CMU CL (17f) appears to have a bug in
    >> GET-INTERNAL-RUN-TIME.

    >> This throws off all profiling.

    >> (get-internal-run-time)

    Tim> This was a bug I remember in 17s.  It's fixed at least in 18a on
    Tim> sparc.

Yes, it's fixed now.  I also (privately) forwarded him some lisp code
that correctly implements get-internal-run-time. (Obtained from
comp.lang.lisp many years ago, I think.)

Ray

From: Gareth McCaughan
Subject: Re: CMUCL bug? get-internal-run-time
Date: Thu, 15 Jul 1999 00:00:00 +0000
Message-ID: <861zeag49o.fsf@g.pet.cam.ac.uk>

Ramachandran Lakshmanan wrote:

> My installed version of CMU CL (17f) appears to have a bug in
> GET-INTERNAL-RUN-TIME.
> 
> This throws off all profiling.
> 
> (get-internal-run-time)
> 
> always returns
> 
> 0
> 
> Anyone have a bug fix?

I don't know about a bug fix, but the version I'm using (18a,
on FreeBSD on x86) seems to return pretty sensible values from
(get-internal-run-time).

-- 
Gareth McCaughan            Dept. of Pure Mathematics & Math. Statistics,
················@pobox.com  Cambridge University, England.