unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Richard Stallman <rms@gnu.org>
Cc: 38492@debbugs.gnu.org, kevin.legouguec@gmail.com
Subject: bug#38492: 27.0.50; Warn pdumper users when pure space has been overflowed
Date: Sun, 15 Dec 2019 15:41:33 -0500	[thread overview]
Message-ID: <jwv8sndmip1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1idS10-0003Z2-N0@fencepost.gnu.org> (Richard Stallman's message of "Fri, 06 Dec 2019 23:48:22 -0500")

> With portable dumping.  I think pure space provides no benefit.

AFAICT, the purespace provides the same benefit with portable dumping as
it does with unexec.  The benefit is to save time during the GC by not
traversing the purespace.  It's basically an "old" generation in a kind
of very restricted form of generational GC.

Maybe purespace is too small compared to typical heap sizes to make
a significant difference, nowadays.


        Stefan






  parent reply	other threads:[~2019-12-15 20:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 19:02 bug#38492: 27.0.50; Warn pdumper users when pure space has been overflowed Kévin Le Gouguec
2019-12-06  8:12 ` Eli Zaretskii
2019-12-06 16:37   ` Kévin Le Gouguec
2019-12-06 16:49     ` Daniel Colascione
2019-12-06 18:51       ` Eli Zaretskii
2019-12-06 19:02         ` dancol
2019-12-07  4:48           ` Richard Stallman
2019-12-07  7:59             ` Eli Zaretskii
2019-12-15 20:41             ` Stefan Monnier [this message]
2019-12-15 20:45               ` Daniel Colascione
2019-12-17  3:09               ` Richard Stallman
2019-12-14 11:42           ` Eli Zaretskii
2019-12-14 14:09             ` Kévin Le Gouguec
2019-12-15 20:33           ` Stefan Monnier
2019-12-15 20:41             ` Daniel Colascione
2019-12-17  3:09             ` Richard Stallman

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=jwv8sndmip1.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=38492@debbugs.gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --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).