From xemacs-m  Mon Jul  7 21:08:45 1997
Received: from altair.xemacs.org (steve@xemacs.miranova.com [206.190.83.19])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id VAA13704
	for <xemacs-beta@xemacs.org>; Mon, 7 Jul 1997 21:08:41 -0500 (CDT)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.6/8.8.6) id TAA31734;
	Mon, 7 Jul 1997 19:11:09 -0700
Mail-Copies-To: never
To: 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>
X-Url: http://www.miranova.com/%7Esteve/
X-Face: #!T9!#9s-3o8)*uHlX{Ug[xW7E7Wr!*L46-OxqMu\xz23v|R9q}lH?cRS{rCNe^'[`^sr5"
 f8*@r4ipO6Jl!:Ccq<xoV[Qz2u8<8-+Vwf2gzJ44lf_/y9OaQ`@#Q65{U4/TC)i2`~/M&QI$X>p:9I
 OSS'2{-)-4wBnVeg0S\O4Al@)uC[pD|+
X-Attribution: sb
From: Steven L Baur <steve@xemacs.org>
In-Reply-To: Hrvoje Niksic's message of "08 Jul 1997 03:33:41 +0200"
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
Date: 07 Jul 1997 19:11:08 -0700
Message-ID: <m2hge6xphf.fsf@altair.xemacs.org>
Lines: 35
X-Mailer: Gnus v5.4.62/XEmacs 20.3(beta12) - "Helsinki"

Hrvoje Niksic <hniksic@srce.hr> writes:

> Steven L Baur <steve@xemacs.org> writes:
>> The build should be changed to only recompile the single file that
>> needs to know the exact array size of the purespace (pure.c) --
>> recompiling alloc.c is unecessary.

> 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?

>> Are you actually short on a cold build ("cold build" == a build after
>> running configure) and getting three links?  If that is the case, then
>> BASE_PURESIZE should definitely be raised (and by more than a few
>> kilobytes).

> 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.  You need to change the
definition of `close enough' in alloc.c.

One thing that might be possible is to add a `tunable.el' to the code
loaded at dump time to control various hardcoded parameters (like the
above mentioned definition of `close enough'.
-- 
steve@calag.com baur
Unsolicited commercial e-mail will be billed at $250/message.

