unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@protonmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Pure space
Date: Sat, 17 Aug 2024 13:51:08 +0300	[thread overview]
Message-ID: <86bk1r2zj7.fsf@gnu.org> (raw)
In-Reply-To: <874j7jk06d.fsf@protonmail.com> (message from Pip Cet on Sat, 17 Aug 2024 08:45:16 +0000)

> Date: Sat, 17 Aug 2024 08:45:16 +0000
> From: Pip Cet <pipcet@protonmail.com>
> Cc: emacs-devel@gnu.org
> 
> "Eli Zaretskii" <eliz@gnu.org> writes:
> 
> >> Date: Fri, 16 Aug 2024 19:07:42 +0000
> >> From: Pip Cet <pipcet@protonmail.com>
> >>
> >> can we revisit the question of whether we still want pure space?
> >
> > We already decided in the past to remove the pure space only when we
> > remove the support for unexec builds.
> 
> IIRC, the situation was that unexec builds were broken on master at the
> point I proposed the pure space removal.  I filed a bug about unexec and
> things were fixed some time later.
> 
> Pure space and unexec aren't closely related at all, and the rebased
> scratch/no-purespace branch, after some tedious fixes, starts fine when
> configured with --with-dumping=unexec.

See my other messages in this thread.

> > So if we no longer want unexec
> > in Emacs 31 and beyond, we can remove pure space (and the unexec build
> > as well) on master.
> 
> What do you think about making pure space overflow fatal as a first
> step?

How would that help?



  reply	other threads:[~2024-08-17 10:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 19:07 Pure space Pip Cet
2024-08-17  6:18 ` Eli Zaretskii
2024-08-17  6:59   ` Stefan Kangas
2024-08-17  8:14     ` Po Lu
2024-08-17 12:10       ` Stefan Kangas
2024-08-17 12:53         ` Eli Zaretskii
2024-08-17 13:36           ` Po Lu
2024-08-17 14:12             ` Eli Zaretskii
2024-08-17  8:45   ` Pip Cet
2024-08-17 10:51     ` Eli Zaretskii [this message]
2024-08-17 11:38       ` Pip Cet
2024-08-17 13:13         ` Eli Zaretskii
2024-08-17 13:26           ` Pip Cet
2024-08-17 14:29             ` Eli Zaretskii
2024-08-17 14:35               ` Pip Cet
2024-08-17 13:11     ` Stefan Kangas
2024-08-17 14:30       ` Pip Cet
2024-08-17 15:34         ` Andrea Corallo
2024-08-17 15:41           ` Pip Cet
2024-08-17  8:16 ` Po Lu
2024-08-17  8:28   ` Po Lu
2024-08-17  8:31     ` Po Lu
2024-08-17  8:57     ` Pip Cet
2024-08-17 11:06       ` Eli Zaretskii
2024-08-17 10:45   ` Eli Zaretskii
2024-08-17 11:46     ` Po Lu
2024-08-17 12:49       ` Eli Zaretskii
2024-08-17 13:44         ` Po Lu
2024-08-17 14:17           ` Eli Zaretskii

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=86bk1r2zj7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.com \
    /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).