From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: emacs-devel@gnu.org
Subject: w32/w64 Emacs and gmalloc()
Date: Fri, 28 Feb 2014 16:39:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20140228T172309-883@post.gmane.org> (raw)
In case it is of interest for the future, I let you know that I have managed
to build an Emacs for w32/w64 that runs without gmalloc.
The patch is far from clean enough to be presented, but the thing is running.
All the problem was about dumping the data.
I did it in an array which is dumped with the executable.
This also removes the need of addsection.
It allows the resulting executable to be striped.
Once the preloaded data are dumped, they are not freed nor realloc'ed, or
rather, the space they occupied is not collected. This is suboptimal, but
there is no way around with the w32 api alone (no way that I know of without
using your own allocator).
After the dumping, the normal emacs runs on the w32 heap management.
Nowadays, the heap can be controlled in various ways, especially it can be
turned into the so-called `low fragmentation heap'.
If anybody has a good benchmark that would be usable to tweak the parameters,
I'll be glad to try it.
Any comments welcome on the pros/cons of this gmalloc removal for w32.
Best regards,
Fabrice
next reply other threads:[~2014-02-28 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 16:39 Fabrice Popineau [this message]
2014-02-28 17:21 ` w32/w64 Emacs and gmalloc() Stefan Monnier
2014-03-01 7:02 ` Eli Zaretskii
2014-03-01 15:50 ` Stefan Monnier
2014-03-01 16:00 ` Fabrice Popineau
2014-03-01 18:08 ` Eli Zaretskii
2014-03-01 20:12 ` Fabrice Popineau
2014-03-01 20:29 ` Eli Zaretskii
2014-03-01 18:05 ` Eli Zaretskii
2014-03-04 3:28 ` Stefan Monnier
2014-03-04 3:49 ` Eli Zaretskii
2014-03-01 6:58 ` Eli Zaretskii
2014-03-01 9:57 ` Fabrice Popineau
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20140228T172309-883@post.gmane.org \
--to=fabrice.popineau@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.