From: Eli Zaretskii <eliz@gnu.org>
Cc: nickrob@snap.net.nz, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: BASE_PURESIZE
Date: Mon, 07 Aug 2006 06:53:38 +0300 [thread overview]
Message-ID: <uu04pdwvx.fsf@gnu.org> (raw)
In-Reply-To: <jebqqx393g.fsf@sykes.suse.de> (message from Andreas Schwab on Sun, 06 Aug 2006 22:25:23 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Cc: eliz@gnu.org, nickrob@snap.net.nz, emacs-devel@gnu.org
> Date: Sun, 06 Aug 2006 22:25:23 +0200
>
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
> > On i686 (2x Intel Xeon 2.40GHz) I get "1245323 pure bytes used".
> > On x86_64 (AMD Athlon 64 3500+) I get "2064768 pure bytes used".
> >
> > Both have the same gcc (GCC) 3.3.4 (pre 3.3.5 20040809) and both are
> > running SuSE 9.2.
>
> On the same systems I only get 1100794/1788523 pure bytes with my usual
> configuration (--with-x-toolkit=lucid).
I still think we _must_ investigate this strange disparity, it's just
that I don't have enough time right now to continue the investigation
I started with Reiner's help. The last thing we've determined was
that the difference happens only when loadup.el loads .elc files, not
.el files. Perhaps someone else could pick up where I left off;
Reiner mentioned that past thread in one of his last messages here.
next prev parent reply other threads:[~2006-08-07 3:53 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 ` 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 ` Eli Zaretskii [this message]
-- 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=uu04pdwvx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=rms@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).