From: Daniel Colascione <dancol@dancol.org>
To: Fejfighter <fejfighter@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: mail@daniel-mendler.de, emacs-devel@gnu.org
Subject: Re: New GC concept
Date: Mon, 21 Jun 2021 15:43:05 -0700 [thread overview]
Message-ID: <5cfabdaa-5cff-cf94-5b4b-3a567ddb3a05@dancol.org> (raw)
In-Reply-To: <CALohuRABgVcsYD36oJ+W=E=3i2WVGhg0o-eugeShhsOBMfwrnA@mail.gmail.com>
On 6/21/21 6:00 AM, Fejfighter wrote:
> Not wanting to see this drop, I found a little time to bring the
> changes up to emacs master with a few notes:
>
> 1) now sits on top of a4fb5811f (Do not attempt to write .elc....)
Awesome. Thanks!
> 2) The C will compile with a couple of warnings as the native comp
> cases are currently not handled.
> 3) There's dead code, commented code and other atrocities on top of
> the current wip
Yep. There were also plenty of atrocities in the original. :-)
> 3) It segfaults during the pdumper step in the build, there is not
> immediately obvious reason for this, but I suspect a move or free
> occurs and it's not tracked
> 4) I have ignored the comments for large_vector and large_vector_meta
> for now, so the meta is kept with the vector struct.
Yeah. That's probably a minor optimization, but we should get around to
completing it. The next big chunk of work is actually implementing
concurrent marking.
> code is up here:
> https://github.com/fejfighter/emacs/tree/feature/newgc
> <https://github.com/fejfighter/emacs/tree/feature/newgc>
> I'm hoping now that it's a little closer to master and compiling
> someone might have a little more luck with the segfault issue I have
> been facing but I will keep try in the mean time,
FWIW, I find rr [1] to be exceptionally useful for diagnosing segfaults
like this.
[1] https://rr-project.org/
next prev parent reply other threads:[~2021-06-21 22:43 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 [this message]
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
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=5cfabdaa-5cff-cf94-5b4b-3a567ddb3a05@dancol.org \
--to=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fejfighter@gmail.com \
--cc=mail@daniel-mendler.de \
/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).