Path: utzoo!utgpu!water!watmath!clyde!rutgers!mcnc!decvax!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!ttds!draken!duvan!drs-ano
From: drs-ano@duvan.nada.kth.se (Gunnar Nordmark)
Newsgroups: comp.sys.amiga
Subject: Re: Gadgets question
Summary: lc2 needs a huge, 88K(!), chunk of continious memory
Message-ID: <280@draken.nada.kth.se>
Date: 29 Jan 88 19:28:58 GMT
References: <4830003@hpiacla.HP.COM>
Sender: usenet@nada.kth.se
Reply-To: drs-ano@duvan.nada.kth.se (Gunnar Nordmark)
Organization: The Royal Inst. of Techn., Stockholm
Lines: 25

In article <4830003@hpiacla.HP.COM> jimg@hpiacla.HP.COM (Jim Garrison) writes:
>Problem #2 -- ASDG FaccII
>
>I'm using a 1000 with 1MB total memory and setting up FaccII with 700 buffers.
>I compile using Lattice 4.0 and everything works fine for awhile.  Then
>suddenly, after 5-10 successful compiles I get a "Cannot Execute LC2" message
>and my compile aborts.  Repeated attempts yield the same results.

I have had this problem with lc2 many times. lc2 doesn't load because there
isn't a sufficiently large memory chunk left. It needs at least 88K of
*continious* memory to load.

>It doesn't appear that I am running out of memory (still at least 68K left).

All I can say is that if lc2 was divided into small hunks of code that could be
loaded into different parts of memory, (like almost every other large program),
none of us would have this stupid problem.

Personaly I suspect the *reason* that lc2 (and lc1) contain these truly HUGE
code hunks is that Lattice want's to press the limits of certain compiler
benchmarks. (Programs with few large hunks loads slightly faster than those
with many small hunks).
I wonder how many microseconds they gained with this approach :-)

  -- Gunnar Nordmark --         NORDMARK@vaxkab.lne.kth.se