From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dancol@dancol.org, pipcet@gmail.com, emacs-devel@gnu.org
Subject: Re: Failing to GC killed buffers considered harmful
Date: Mon, 30 Mar 2020 21:51:48 +0300 [thread overview]
Message-ID: <83eet93ccb.fsf@gnu.org> (raw)
In-Reply-To: <jwvftdpog14.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 30 Mar 2020 14:32:30 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>, Daniel Colascione <dancol@dancol.org>,
> emacs-devel@gnu.org
> Date: Mon, 30 Mar 2020 14:32:30 -0400
>
> > FWIW, maybe we should get rid of all_buffers.
> > AFAICT the only reason we need it is to unmark the buffers during the
> > sweep phase, and we could allocate buffers like any other
> > pseudovector instead.
>
> The patch below seems to work.
>
> The only worrisome part I think is that `live_buffer_holding` allowed
> pointers into buffer objects, whereas `live_vector_p` only treats
> pointers to the beginning of the object as a valid reference.
>
> Not sure why buffers would be more likely to have valid pointers into
> them (and can't remember discussions about that either), so I assume the
> difference was not important (it just happened to be easier to support
> that for buffers).
>
> Any objection?
What are the advantages? The original problem is solved, and
everybody agreed that having a dead buffer in the pdumped area is
nothing we should bother about.
next prev parent reply other threads:[~2020-03-30 18:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 14:23 Failing to GC killed buffers considered harmful Eli Zaretskii
2020-03-29 16:45 ` Stefan Monnier
2020-03-29 18:54 ` Eli Zaretskii
2020-03-29 19:06 ` Daniel Colascione
2020-03-29 19:24 ` Eli Zaretskii
2020-03-29 16:46 ` Pip Cet
2020-03-29 18:48 ` Eli Zaretskii
2020-03-29 19:07 ` Pip Cet
2020-03-29 19:12 ` Daniel Colascione
2020-03-29 19:25 ` Pip Cet
2020-03-29 19:28 ` Eli Zaretskii
2020-03-30 15:36 ` Pip Cet
2020-03-30 15:53 ` dancol
2020-03-30 17:07 ` Stefan Monnier
2020-03-30 17:02 ` Stefan Monnier
2020-03-30 18:32 ` Stefan Monnier
2020-03-30 18:51 ` Eli Zaretskii [this message]
2020-03-30 19:14 ` Daniel Colascione
2020-03-30 19:40 ` Stefan Monnier
2020-03-31 14:07 ` Eli Zaretskii
2020-03-31 14:09 ` Eli Zaretskii
2020-03-31 21:57 ` Stefan Monnier
2020-03-31 14:58 ` Pip Cet
2020-03-31 16:52 ` Stefan Monnier
2020-03-31 18:23 ` Pip Cet
2020-03-31 19:20 ` 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=83eet93ccb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@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.