From: Christoph <cschol2112@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Windows: Emacs 24.1 binary size vs 24.2 binary size
Date: Mon, 10 Sep 2012 23:00:54 -0600 [thread overview]
Message-ID: <CAOrdkqOp85uDMsqG+Wnat-UD2XuvQ+WHSkzrFJv4ya3ygNzPOw@mail.gmail.com> (raw)
In-Reply-To: <jwvmx0yj5ig.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Mon, Sep 10, 2012 at 8:58 AM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> That sounds weird, indeed. An explanation that comes to my mind
> goes along the following lines:
>
> little change in code
> => slight change in some part of the dump process
> => memory allocation pattern at that point is different
> => some memory zone that used to be `free'able now can't be freed any
> more because some surviving object is now placed in that zone rather
> in some other zone.
Interesting.
>
IOW the actual live data is pretty much the same, but the larger binary
> has a lot more memory that's "allocated from the OS but kept in some
> free list". How do the
>
> Pure-hashed: <FOO>
> Dumping under the name emacs
> <BAR> pure bytes used
>
> compare between the two builds?
I'll check and report back.
[-- Attachment #2: Type: text/html, Size: 1476 bytes --]
next prev parent reply other threads:[~2012-09-11 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 2:20 Windows: Emacs 24.1 binary size vs 24.2 binary size Christoph Scholtes
2012-09-01 14:21 ` Christoph Scholtes
2012-09-01 14:50 ` Eli Zaretskii
2012-09-08 13:33 ` Christoph Scholtes
2012-09-10 2:42 ` Christoph
2012-09-10 4:52 ` Eli Zaretskii
2012-09-10 12:26 ` Christoph
2012-09-10 14:58 ` Stefan Monnier
2012-09-11 5:00 ` Christoph [this message]
2012-09-01 14:56 ` Óscar Fuentes
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=CAOrdkqOp85uDMsqG+Wnat-UD2XuvQ+WHSkzrFJv4ya3ygNzPOw@mail.gmail.com \
--to=cschol2112@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).