From: Jonas Hahnfeld via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>, guile-devel@gnu.org
Subject: Re: GC + Java finalization
Date: Fri, 19 Nov 2021 20:01:55 +0100 [thread overview]
Message-ID: <241b7e993d1d30a1fde808145024f13802ed4553.camel@hahnjo.de> (raw)
In-Reply-To: <98d5fd3f1735e9a04b7d06c0054240cc378cb528.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 3099 bytes --]
Am Freitag, dem 19.11.2021 um 18:48 +0000 schrieb Maxime Devos:
> Jonas Hahnfeld schreef op vr 19-11-2021 om 15:52 [+0100]:
> > Am Freitag, dem 19.11.2021 um 14:14 +0000 schrieb Maxime Devos:
> > > [...]
> > >
> > > From your other responses, I now know it is actually related to
> > > (non-
> > > )Java style finalisation, but my comment about ‘separate patch’
> > > still
> > > seems to apply:
> > >
> > > >
> > > > Again, as replied in July to the same comment, it *is* a separate
> > > > patch for exactly this reason.
> > >
> > > More concretely, it is in the same patch as that modified
> > > libguile/random.c. The patch to libguile/random.c doesn't seem to
> > > be for non-Java finalization reasons. Going by the commit message,
> > > the only possible reason I could find is:
> > >
> > > ‘There is no point in registering memory with the garbage collector
> > > if it doesn't need to do its job’
> > >
> > > But I don't see any ‘registering memory’, only replacing
> > > scm_gc_calloc+scm_gc_free by scm_calloc+free, and without any
> > > finalisation in sight. Unless you mean with ‘registering memory’
> > > the "random bignum chunks" argument. But that still seems unrelated
> > > to non-Java finalization.
> >
> > Any memory allocation through gc implicitly registers the memory.
>
> I don't mean what you mean with ‘registering memory’. I don't
> see that phrase anywhere at <https://www.hboehm.info/gc/#details>
> or <https://www.hboehm.info/gc/faq.html>. I only know about
> registering finalisers, but not about registering memory.
Maybe it's not an official term; I call it "registration" because the
garbage collector has to keep track of all memory segments it handed
out, so it "registers" the allocation in a data structure somewhere.
> Also, I'm not sure what you are trying to say here and in the following
> paragraph. Is this some kind of argument for why the change to
> libguile/random.c should be in the same patch, or general explanation,
> ...?
Both changes address the same issue of removing matching calls to
scm_gc_alloc+scm_gc_free. That's why I think it's one logical change,
even though one is actually a problem when disabling Java-style
finalization - it makes sense even without the following patch.
>
> > Both changes are unrelated to finalization, they are there to avoid this
> > unnecessary registration.
> Thanks for the clarification, though I have no idea what ‘registration’
> is ...
> > My previous replies only tried to clarify why
> > any other solution is worse.
>
> ... but what problem and what replies are you referring to here?
> I haven't seen any e-mails explaining GC problems in libguile/random.c.
> I only have seen replies about non-Java style finalisation, which
> do not apply to libguile/random.c (no objects but the stack have a
> reference to random_chunks anywhere and libguile/random.c is not
> playing with finalizers).
Yes, the one in libguile/random.c is just unnecessary, probably not
actually a problem.
Jonas
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-11-19 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 12:05 GC + Java finalization Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-07-03 17:14 ` Maxime Devos
2021-07-03 17:26 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-07-03 18:49 ` Maxime Devos
2021-07-03 18:54 ` Maxime Devos
2021-07-15 18:44 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-10-10 16:22 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 12:18 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2022-02-22 10:14 ` Dr. Arne Babenhauserheide
2022-02-22 15:12 ` Mike Gran
2021-11-19 13:13 ` Maxime Devos
2021-11-19 13:32 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:35 ` Maxime Devos
2021-11-19 13:40 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:44 ` Maxime Devos
2021-11-19 13:53 ` Maxime Devos
2021-11-19 13:53 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:01 ` Maxime Devos
2021-11-19 13:48 ` Maxime Devos
2021-11-19 13:55 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:14 ` Maxime Devos
2021-11-19 14:52 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 18:48 ` Maxime Devos
2021-11-19 19:01 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library [this message]
2021-11-19 13:15 ` Maxime Devos
2021-11-19 13:35 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 14:21 ` Maxime Devos
2021-11-19 15:32 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-19 13:17 ` Maxime Devos
2021-11-19 13:38 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2021-11-20 9:19 ` Maxime Devos
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=241b7e993d1d30a1fde808145024f13802ed4553.camel@hahnjo.de \
--to=guile-devel@gnu.org \
--cc=hahnjo@hahnjo.de \
--cc=maximedevos@telenet.be \
/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.
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).