From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: eliz@gnu.org, nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: BASE_PURESIZE
Date: Sun, 06 Aug 2006 11:19:23 +0200 [thread overview]
Message-ID: <v9r6zu1ask.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1G9aUT-0005FD-8K@fencepost.gnu.org> (Richard Stallman's message of "Sun, 06 Aug 2006 00:43:53 -0400")
On Sun, Aug 06 2006, Richard Stallman wrote:
> For the 2006-07-29 sources, I need 150000 extra bytes on my SUSE 10.0
> installation:
> 1102000 is the default BASE_PURESIZE. During dumping, I get:
> 1243908 pure bytes used
>
> That's more or less what it used before the optimizations. It sounds
> like something is wrong, and those optimizations are not working in
> your case.
That's possible. Until mid of June (some weeks before the
optimizations), the default value was sufficient on this machine
(Pentium M 1500MHz; gcc (GCC) 4.0.2 20050901 (prerelease); SUSE 10.0).
I didn't update the sources often on this host, so I'm not sure when
got the overflow the first time.
On the other machines, I had to add some extra space at least since
April. See the thread "PURESIZE increased (again)" (April-June)
<URL:http://thread.gmane.org/v9d5diibsr.fsf%40marauder.physik.uni-ulm.de>.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-08-06 9:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 2:16 BASE_PURESIZE Nick Roberts
2006-08-05 9:41 ` BASE_PURESIZE Eli Zaretskii
2006-08-05 16:23 ` BASE_PURESIZE Reiner Steib
2006-08-05 18:51 ` BASE_PURESIZE Richard Stallman
2006-08-05 20:07 ` BASE_PURESIZE Reiner Steib
2006-08-06 4:43 ` BASE_PURESIZE Richard Stallman
2006-08-06 9:19 ` Reiner Steib [this message]
2006-08-06 19:40 ` BASE_PURESIZE Reiner Steib
[not found] ` <jebqqx393g.fsf@sykes.suse.de>
2006-08-07 3:53 ` BASE_PURESIZE Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2009-10-23 11:00 BASE_PURESIZE Eli Zaretskii
2009-10-23 11:39 ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:10 ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:24 ` BASE_PURESIZE Andreas Schwab
2009-10-23 14:35 ` BASE_PURESIZE Eli Zaretskii
2009-10-23 14:50 ` BASE_PURESIZE Andreas Schwab
2009-10-24 10:05 ` BASE_PURESIZE Eli Zaretskii
2009-10-24 10:37 ` BASE_PURESIZE Andreas Schwab
2009-10-24 13:18 ` BASE_PURESIZE Eli Zaretskii
2009-10-24 17:27 ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 19:01 ` BASE_PURESIZE Stefan Monnier
2009-10-25 8:24 ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 19:04 ` BASE_PURESIZE Chong Yidong
2009-10-24 19:16 ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 11:58 ` BASE_PURESIZE Dan Nicolaescu
2009-10-23 14:24 ` BASE_PURESIZE Juanma Barranquero
2009-10-24 4:41 ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24 6:47 ` BASE_PURESIZE Dan Nicolaescu
2009-10-24 8:24 ` BASE_PURESIZE Stephen J. Turnbull
2009-10-24 10:22 ` BASE_PURESIZE Eli Zaretskii
2009-10-24 11:14 ` BASE_PURESIZE Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9r6zu1ask.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).