Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!ncar!oddjob!uxc!uxc.cso.uiuc.edu!a.cs.uiuc.edu!m.cs.uiuc.edu!roch
From: roch@m.cs.uiuc.edu
Newsgroups: comp.sys.amiga
Subject: Re: SBProlog memory requirements
Message-ID: <7200050@m.cs.uiuc.edu>
Date: 27 Jul 88 14:19:00 GMT
References: <3501@louie.udel.EDU>
Lines: 36
Nf-ID: #R:louie.udel.EDU:3501:m.cs.uiuc.edu:7200050:000:1185
Nf-From: m.cs.uiuc.edu!roch    Jul 27 09:19:00 1988



In regards to running Stony Brook Prolog on a one meg
machine:

No, you don't need to recompile.  In the manual, several
switches are described (see simulator options) which
control the amount of memory to be allocated.  This
is in section 7.2 (page 57 in my troffed manual).  The
two that you should tinker with are:

-m size1 -p size2

Size1 and size2 should be integers telling how many 32
bit words should be allocated to:

	-m the local stack and heap
	-p the program area

They both default to 100000 words.  Also the trail
stack may be set using the -b size3 option.  By
default, it is set to the size of the local stack
and heap / 5.  Each of these allocations request 
contiguous blocks, so if your memory is fragmented
(e.g. you just finished playing destroy the universe,
before you were hacking away with mg, ...) chances
are that there won't be any blocks large enough.
By the way, does anyone know if there's a way to
force the OS to merge all adjacent free blocks?

For starters, I'd try setting -m and -p to 50000,
but you have problems if you're using a lot of
the library code (e.g. compiling might not work).

				Good luck,
				david roch
				roch@a.cs.uiuc.edu