From xemacs-m  Wed Mar 19 01:16:08 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 BAA23399
	for <xemacs-beta@xemacs.org>; Wed, 19 Mar 1997 01:16:07 -0600 (CST)
Received: (from steve@localhost)
	by altair.xemacs.org (8.8.5/8.8.5) id XAA06371;
	Tue, 18 Mar 1997 23:27:56 -0800
Mail-Copies-To: never
To: xemacs-beta@xemacs.org
Subject: Re: [19.15-b100] Build report: ok on FreeBSD 2.1.5
References: <m0w7APc-000024C@susan.logware.de>
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@miranova.com>
In-Reply-To: Michael Diers's message of Wed, 19 Mar 97 02:43 MET
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
Date: 18 Mar 1997 23:27:53 -0800
Message-ID: <m2d8swe3ye.fsf@altair.xemacs.org>
Lines: 59
X-Mailer: Gnus v5.4.30/XEmacs 20.1(beta9)

Michael Diers writes:

> There's only one odd thing I noticed. Computing puresize
> requirements, the first guess is too low (as expected); the second
> guess fits like a glove (as expected?), but there's an error
> returned. Then, there's a third and _final_ try resulting in 7%
> loss...

Your edited output doesn't make sense.

> Here's the edited make output:

>     [...]
>     Dumping under names xemacs and emacs-19.15-xemacs-beta100

>     ****	Pure Lisp storage exhausted!
>             Purespace usage: 629044 of 625000
>     ****
>     [...]
>     XEmacs: Pure size adjusted, will restart `make'
>     [...]
>     Dumping under names xemacs and emacs-19.15-xemacs-beta100
>     Purespace usage: 629008 of 629044 (100%).
>     [...]
>     *** Error code 1 (ignored)

What does XEmacs print prior to this?  Due to string compaction during 
dump the amount of lossage when pure space is too small is less
precisely computed than when it is too high.  If you are seeing a
`XEmacs: Pure size adjusted, will restart `make'' message, then all is 
well.  It is known[1] that the build will generally take three passes
when the puresize starts out too small.

The first build starts out too small, the second build ends up too
high because string compaction isn't taken into effect, the third
build is just right.  That is the normal procedure unless someone
wishes to take the time to compile with just the permutation of
various options set to determine the numbers.

>     cd src; make dump-elcs    CC='gcc' CFLAGS='-g -O2 -m486
>     -fno-strength-reduce -pipe' MAKE='make'
>     [...]
>     Bootstrapping from temacs...
>     Purespace usage: 41844 of 629044 (7% -- 573k wasted).
                       ^^^^^
>     [...]

Those numbers are indicative of what you should see when .els and not
.elcs are being loaded.  You have something like 2k of threshold
between what XEmacs thinks you should have a

[1]
I think it makes the most sense to guess way too high first so that
XEmacs can make a precise determination of space needs and require
only two builds to get an exact number, but I was overruled and that's
water under the bridge now.
-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.

