From: Helmut Eller <eller.helmut@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, Pip Cet <pipcet@protonmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Merging scratch/no-purespace to remove unexec and purespace
Date: Tue, 17 Dec 2024 20:30:38 +0100 [thread overview]
Message-ID: <87zfku6ra9.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmmX7pxzLCRU3aU=oZS1NRdVuxxU-JCHpO2=e3J-mRS55Q@mail.gmail.com> (Stefan Kangas's message of "Tue, 17 Dec 2024 10:47:24 +0000")
On Tue, Dec 17 2024, Stefan Kangas wrote:
[...]
> We, the maintainers, believe that the scratch/no-purespace branch is
> now ready to merge, and would appreciate any final feedback, testing,
> and code reviews. Specifically, the branch has been primarily tested
> on GNU/Linux and macOS, so testing on other systems would be greatly
> appreciated.
Do you have an estimate what removing purespace will cost in terms of GC
time? I mean something like "1ms per collection". Or perhaps a
suggestion how I could measure it?
next prev parent reply other threads:[~2024-12-17 19:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 10:47 Merging scratch/no-purespace to remove unexec and purespace Stefan Kangas
2024-12-17 13:12 ` Gerd Möllmann
2024-12-17 14:20 ` Gerd Möllmann
2024-12-17 14:30 ` Gerd Möllmann
2024-12-17 17:56 ` Gerd Möllmann
2024-12-17 18:50 ` Eli Zaretskii
2024-12-17 18:56 ` Gerd Möllmann
2024-12-18 12:55 ` Andrea Corallo
2024-12-18 14:03 ` Gerd Möllmann
2024-12-18 16:05 ` Pip Cet via Emacs development discussions.
2024-12-18 16:30 ` Gerd Möllmann
2024-12-18 16:25 ` Pip Cet via Emacs development discussions.
2024-12-18 22:27 ` Andrea Corallo
2024-12-19 9:28 ` Pip Cet via Emacs development discussions.
2024-12-19 10:38 ` Andrea Corallo
2024-12-19 10:50 ` Stefan Kangas
2024-12-19 12:08 ` Pip Cet via Emacs development discussions.
2024-12-19 17:55 ` Stefan Kangas
2024-12-19 20:13 ` Pip Cet via Emacs development discussions.
2024-12-20 15:59 ` Stefan Monnier
2024-12-20 16:22 ` Pip Cet via Emacs development discussions.
2024-12-20 17:25 ` Gerd Möllmann
2024-12-20 20:35 ` Andrea Corallo
2024-12-20 20:39 ` Pip Cet via Emacs development discussions.
2024-12-21 6:33 ` Gerd Möllmann
2024-12-21 6:56 ` Andrea Corallo
2024-12-20 20:38 ` Pip Cet via Emacs development discussions.
2024-12-20 20:57 ` Gerd Möllmann
2024-12-20 8:42 ` Pip Cet via Emacs development discussions.
2024-12-18 0:18 ` Stefan Kangas
2024-12-17 19:30 ` Helmut Eller [this message]
2024-12-17 20:47 ` Stefan Monnier
2024-12-18 2:15 ` Stefan Kangas
2024-12-18 7:11 ` Helmut Eller
2024-12-18 13:35 ` Pip Cet via Emacs development discussions.
2024-12-18 6:56 ` Helmut Eller
2024-12-21 17:41 ` Helmut Eller
2024-12-21 18:32 ` Gerd Möllmann
2024-12-22 1:28 ` Stefan Kangas
2024-12-18 9:30 ` Pip Cet via Emacs development discussions.
2024-12-18 0:50 ` Po Lu
2024-12-18 2:12 ` Stefan Kangas
2024-12-18 21:26 ` Stefan Monnier
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=87zfku6ra9.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@protonmail.com \
--cc=stefankangas@gmail.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 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.