GNU bug report logs - #78662
feature/igc: [PATCH] Make buffer_local_symbols exact roots

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Pip Cet <pipcet <at> protonmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#78662: closed (feature/igc: [PATCH] Make buffer_local_symbols
 exact roots)
Date: Sun, 01 Jun 2025 09:31:06 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sun, 01 Jun 2025 09:29:55 +0000
with message-id <87sekjern4.fsf <at> protonmail.com>
and subject line Re: bug#78662: feature/igc: [PATCH] Make buffer_local_symbols exact roots
has caused the debbugs.gnu.org bug report #78662,
regarding feature/igc: [PATCH] Make buffer_local_symbols exact roots
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
78662: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78662
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Helmut Eller <eller.helmut <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: feature/igc: [PATCH] Make buffer_local_symbols exact roots
Date: Sun, 01 Jun 2025 10:37:04 +0200

[Message part 3 (text/plain, inline)]

Tracing buffer_local_symbols and buffer_defaults exactly as in
the patch seems to work.

[0001-Make-buffer_defaults-and-buffer_local_symbols-exact-.patch (text/x-diff, attachment)]

[Message part 5 (message/rfc822, inline)]

From: Pip Cet <pipcet <at> protonmail.com>
To: Helmut Eller <eller.helmut <at> gmail.com>
Cc: 78662-done <at> debbugs.gnu.org
Subject: Re: bug#78662: feature/igc: [PATCH] Make buffer_local_symbols exact
 roots
Date: Sun, 01 Jun 2025 09:29:55 +0000

"Helmut Eller" <eller.helmut <at> gmail.com> writes:

> Tracing buffer_local_symbols and buffer_defaults exactly as in
> the patch seems to work.

Thanks.  I see no reason why it wouldn't work, and it doesn't crash, so
I've pushed it and am closing the bug.

I did note that buffer_defaults.text changes from NULL to
&buffer_defaults.own_text on the first scan, but this seems harmless to
me.

If these strange objects (no MPS header, these two have a vectorlike
header but buffer_local_flags doesn't, not necessarily lisp-aligned)
cause any trouble, we could always allocate them on the MPS heap, giving
us the very slight benefit of putting some words behind a barrier.

Pip

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.