From: Eli Zaretskii <eliz@gnu.org>
To: Daniele Nicolodi <daniele@grinta.net>
Cc: emacs-devel@gnu.org
Subject: Re: New GC concept
Date: Tue, 08 Jun 2021 05:22:43 +0300 [thread overview]
Message-ID: <83k0n5f630.fsf@gnu.org> (raw)
In-Reply-To: <29607b7f-2286-c8c4-a693-cc715a4c26d4@grinta.net> (message from Daniele Nicolodi on Mon, 7 Jun 2021 21:51:45 +0200)
> From: Daniele Nicolodi <daniele@grinta.net>
> Date: Mon, 7 Jun 2021 21:51:45 +0200
>
> > We can definitely replace the existing GC with the new GC everywhere.
> > I've designed the new GC to work on systems without virtual memory
> > facilities. On these systems, we'll have to run the GC in
> > non-concurrent, non-generational mode, but that's no regression from
> > what we have today. We'll also probably want to use a smaller block size
> > on these systems to reduce fragmentation overhead.
>
> Isn't DOS the only system in this class? (It is not a rhetorical
> question: a while ago I asked which systems are officially supports and
> the answer was that all systems that currently run Emacs are supported).
>
> Does it make sense to still support DOS?
The development environment which is used to build the MS-DOS port of
Emacs (DJGPP) does support virtual memory (IIUC what that means in
this context).
next prev parent reply other threads:[~2021-06-08 2:22 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
2021-06-07 18:03 ` Daniel Colascione
2021-06-07 19:51 ` Daniele Nicolodi
2021-06-08 2:22 ` Eli Zaretskii [this message]
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=83k0n5f630.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=daniele@grinta.net \
--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).