unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nix <nix@esperi.org.uk>
To: Richard Stallman <rms@gnu.org>
Cc: esr@thyrsus.com, Eli Zaretskii <eliz@gnu.org>,
	"Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>,
	emacs-devel@gnu.org
Subject: Re: Time to drop the pre-dump phase in the build?
Date: Sun, 12 Jan 2014 00:16:17 +0000	[thread overview]
Message-ID: <87r48ehx66.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <E1W1sog-0006vy-GZ@fencepost.gnu.org> (Richard Stallman's message of "Sat, 11 Jan 2014 02:17:10 -0500")

On 11 Jan 2014, Richard Stallman outgrape:
> 20 years ago we needed to port the dumping code to various different
> systems.  It was substantial work.  But it seems there have been no new
> such systems in a long time, and that code seems to be stable.

It still requires substantial ugly hacks, e.g. there is code in glibc to
serialize and deserialize malloc state whose sole purpose is to support
Emacs dumping, and which cannot be changed since that would force Emacs
to be redumped when glibc was upgraded. It seems plausible that this
might eventually retard glibc allocator development :(

XEmacs long ago migrated to a 'portable undumper', whereby (IIRC) the
Lisp heap is serialized into a form that is then mmap()ed in at startup
time (using a separate file, so unexec() is no longer necessary). It was
a lot of work, but doing something similar might be worth considering in
the future anyway.

-- 
NULL && (void)



  reply	other threads:[~2014-01-12  0:16 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 19:15 Time to drop the pre-dump phase in the build? Eric S. Raymond
2014-01-10 19:49 ` Eli Zaretskii
2014-01-11  6:16   ` Paul Eggert
2014-01-11  7:17   ` Richard Stallman
2014-01-12  0:16     ` Nix [this message]
2014-01-12  3:48       ` Eli Zaretskii
2014-01-12  3:53         ` Eric S. Raymond
2014-01-11  7:17   ` Richard Stallman
2014-01-10 19:51 ` Stefan Monnier
2014-01-10 20:09   ` Eric S. Raymond
2014-01-10 20:13   ` Eli Zaretskii
2014-01-10 20:20 ` Barry Warsaw
2014-01-10 20:30   ` Eli Zaretskii
2014-01-10 21:06     ` Barry Warsaw
2014-01-10 22:19 ` Daniel Colascione
2014-01-10 22:58   ` David Kastrup
2014-01-11  0:05     ` Daniel Colascione
2014-01-10 23:23   ` Stefan Monnier
2014-01-11  0:07     ` Daniel Colascione
2014-01-11  2:58       ` Stefan Monnier
2014-01-11  3:37         ` Daniel Colascione
2014-01-11  5:13           ` Stefan Monnier
2014-01-11  5:30             ` Daniel Colascione
2014-01-11 16:14           ` Stephen J. Turnbull
2014-01-11 20:13     ` Glenn Morris

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=87r48ehx66.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=rms@gnu.org \
    --cc=turnbull@sk.tsukuba.ac.jp \
    /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).