From: Dan Nicolaescu <dann@ics.uci.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: BASE_PURESIZE
Date: Fri, 23 Oct 2009 04:58:30 -0700 (PDT) [thread overview]
Message-ID: <200910231158.n9NBwUS2027817@godzilla.ics.uci.edu> (raw)
In-Reply-To: <8363a6gytm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Oct 2009 13:00:05 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Isn't the current definition of BASE_PURESIZE too large?
>
> #define BASE_PURESIZE (1430000 + SYSTEM_PURESIZE_EXTRA + SITELOAD_PURESIZE_EXTRA)
>
> I looked at the values of pure_size vs pure_bytes_used in several
> builds on several platforms, and I see that we are wasting at least
> 130KB:
>
> MS-Windows:
> (gdb) p pure_size
> $1 = 1480000
> (gdb) p pure_bytes_used
> $2 = 1357888
>
> 64-bit GNU/Linux (--without-x):
> (gdb) p pure_size
> $1 = 2383333
> (gdb) p pure_bytes_used
> $2 = 2015813
>
> 64-bit GNU/Linux (with X):
> (gdb) p pure_size
> $1 = 2383333
> (gdb) p pure_bytes_used
> $2 = 2193049
>
> MS-DOS:
> (gdb) p pure_size
> $1 = 1440000
> (gdb) p pure_bytes_used
> $2 = 1275442
>
> GNU/Linux without-X is the extreme example: it wastes 370KB.
>
> How about reducing the 1430000 number above?
I have a few pending changes that will make the sizes needed just under
that, no need to fiddle with it all the time.
next prev parent reply other threads:[~2009-10-23 11:58 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
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-30 1:17 ` defcustom standard-value (was: Re: 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 ` Dan Nicolaescu [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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 ` BASE_PURESIZE Reiner Steib
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
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=200910231158.n9NBwUS2027817@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).