From: Matt Armstrong <matt@rfc20.org>
To: Daniel Colascione <dancol@dancol.org>, emacs-devel@gnu.org
Subject: Re: New GC concept
Date: Mon, 07 Jun 2021 10:32:01 -0700 [thread overview]
Message-ID: <874ke9h97y.fsf@rfc20.org> (raw)
In-Reply-To: <bc4c03f1-5c6a-ab6c-acb1-4cee90a4b462@dancol.org>
Daniel Colascione <dancol@dancol.org> writes:
> Emacs has had the same GC for a decent amount of time now (since the
> 1980s, really). I spent some time in 2020 rewriting it from scratch. I
> haven't had time to work on the new GC recently, but I figure I'd throw
> it out here to get some feedback on the general concept.
>
> Check out
> https://github.com/dcolascione/emacs-1/blob/newgc-wip/src/alloc.c,
> specifically the big doc comment on top
Hey Daniel, I am no GC expert but I'm liking this a lot. I love the
block comments in your alloc.c -- very clear and easy to understand.
You're in a uniquely good position to work on this. I hope you
continue!
I'm curious about the answer to one of the unanswered questions in your
alloc.c FAQ: What about systems without virtual memory? Asked another
way: can we reasonably expect to entirely replace the current GC with
this new one? Are there platforms Emacs supports today that would be
left behind?
next prev parent reply other threads:[~2021-06-07 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 3:30 New GC concept Daniel Colascione
2021-06-04 8:00 ` Daniel Mendler
2021-06-04 9:47 ` Daniel Colascione
2021-06-04 10:50 ` Eli Zaretskii
2021-06-21 13:00 ` Fejfighter
2021-06-21 13:31 ` Eli Zaretskii
2021-06-21 22:43 ` Daniel Colascione
2021-07-24 13:39 ` Fejfighter
2021-06-04 11:06 ` Daniel Mendler
2021-06-04 8:56 ` Andrea Corallo via Emacs development discussions.
2021-06-07 17:32 ` Matt Armstrong [this message]
2021-06-07 18:03 ` Daniel Colascione
2021-06-07 19:51 ` Daniele Nicolodi
2021-06-08 2:22 ` Eli Zaretskii
2021-06-21 22:58 ` Daniel Colascione
2021-06-22 12:59 ` 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=874ke9h97y.fsf@rfc20.org \
--to=matt@rfc20.org \
--cc=dancol@dancol.org \
--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 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).