This is the mail archive of the
mailing list for the GCC project.
Re: GC changes
- To: tej at melbpc dot org dot au
- Subject: Re: GC changes
- From: Geoff Keating <geoffk at geoffk dot org>
- Date: Thu, 11 Jan 2001 13:17:58 -0800
- CC: gcc at gcc dot gnu dot org
- References: <3A5E18C1.1D23DEE1@melbpc.org.au>
- Reply-to: Geoff Keating <geoffk at redhat dot com>
> Date: Fri, 12 Jan 2001 07:34:09 +1100
> From: Tim Josling <firstname.lastname@example.org>
> Here we are building a GCable structure. Once it is all linked
> into the main trees under the roots and visible to the mark
> routines, it will not disappear during GC. But until then, it is
> vulnerable to GC, which can be triggered on any memory
> allocation. Here there seem to be several memory allocations and
> the early ones are unprotected.
I believe that at present GC is triggered only when ggc_collect() is called.
- Geoffrey Keating <email@example.com>