Newsgroups: comp.lang.lisp
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Subject: Re: Any Suggestions for Read-Write-Area of Lucid Sun Common Lisp 3.0.1?
Message-ID: <1991May1.193431.6482@Think.COM>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
References: <461@tansei1.tansei.cc.u-tokyo.ac.jp>
Date: Wed, 1 May 91 19:34:31 GMT

In article <461@tansei1.tansei.cc.u-tokyo.ac.jp> d34676@tansei.cc.u-tokyo.ac.jp (Akira Kurihara) writes:
>I am porting a Common Lisp program from Macintosh Allegro Common
>Lisp 1.3.2 (MACL) to Lucid Sun Common Lisp 3.0.1 (SunCL). Please give me
>some suggestions!

I'm not sure how useful this suggestion will be: upgrade to version 4.0,
and get the patch to bug 5648.  I believe this bug refers to a whole bunch
of problems reported in the Ephemeral GC.

By the way, when you're estimating the memory use of your program, don't
forget to count all the intermediate data.  You mentioned that your
application uses integers up to 10^40, so you're probably consing lots of
temporary bignums.  These should get collected by the EGC, but perhaps the
bugs in EGC are causing your problem.

If you can't upgrade to 4.0, maybe there is a similar patch available for
3.0; ask Lucid.  By the way, the latest patch level of 3.0 is 3.0.5, but
you're still running 3.0.1; you should at least try to get the latest set
of patches for your version.

--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar