From xemacs-m  Mon Jul  7 21:41:30 1997
Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA14018
	for <xemacs-beta@xemacs.org>; Mon, 7 Jul 1997 21:41:29 -0500 (CDT)
Received: (from hniksic@localhost)
          by jagor.srce.hr (8.8.5/8.8.4)
	  id EAA15901; Tue, 8 Jul 1997 04:41:29 +0200 (MET DST)
To: XEmacs Developers <xemacs-beta@xemacs.org>
Subject: Re: Too small PURESIZE
References: <kig205a1kb5.fsf@jagor.srce.hr> <m2k9j2z8vj.fsf@altair.xemacs.org> <kigen9atm2b.fsf@jagor.srce.hr> <m2205az6qi.fsf@altair.xemacs.org> <kig3epqtjii.fsf@jagor.srce.hr> <m2hge6xphf.fsf@altair.xemacs.org>
X-Attribution: Hrv
X-Face: Mie8:rOV<\c/~z{s.X4A{!?vY7{drJ([U]0O=W/<W*SMo/Mv:58:*_y~ki>xDi&N7XG
        KV^$k0m3Oe/)'e%3=$PCR&3ITUXH,cK>]bci&<qQ>Ff%x_>1`T(+M2Gg/fgndU%k*ft
        [(7._6e0n-V%|%'[c|q:;}td$#INd+;?!-V=c8Pqf}3J
From: Hrvoje Niksic <hniksic@srce.hr>
Date: 08 Jul 1997 04:41:29 +0200
In-Reply-To: Steven L Baur's message of "07 Jul 1997 19:11:08 -0700"
Message-ID: <kigu3i6s1t2.fsf@jagor.srce.hr>
Lines: 46
X-Mailer: Gnus v5.4.59/XEmacs 20.3(beta11) - "Stockholm"

Steven L Baur <steve@xemacs.org> writes:

> > True.  I don't even understand why alloc.c is being recompiled.
> 
> It includes puresize.h which includes puresize-adjust.h.  I think
> the logic at the very bottom of puresize.h can be moved safely to
> pure.c.  Maybe with so much broken, now would be a good time to try
> moving it?

To avoid recompiling alloc.c, it would have to not include
puresize.h.  This would also mean that alloc.c does not know the
PURESIZE.  Will it be able to function without knowing it?  Can all
the stuff that needs to know PURESIZE be moved to pure.c?

> > No, I'm getting two links on cold build, which seems to be correct.
> > Still, I'd like for a way to get one link only -- and the second only
> > if puresize is *really* insufficient -- like, if you add preloaded
> > stuff.
> 
> > Would that be possible?
> 
> So long as the BASE_PURESIZE is set high enough, yes at the price of
> an arbitrary amount of unused purespace.

If this arbitrary amount is under 10K or so, this sounds like a good
idea to me.

> You need to change the definition of `close enough' in alloc.c.

I don't know what you mean; the code in alloc.c (in `check_purespace',
to be precise) only checks whether the purespace has been exhausted,
as reported by PURESIZE and pureptr.  The only way to make it not
exhausted by default is to increase PURESIZE.  And the easiest way to
do that is to adjust BASE_PURESIZE.

Do you think we should go for it?  I think it would be worth wasting a 
few K of memory for the decrease in confusion and complexity.

Of course, if a site administrator adds stuff to dumped-lisp, the
puresize adjustment mechanism will keep functioning -- so we'll still
be better off than we were without it.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
ED WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS!!

