This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Potential GC problem on the 3.3 branch
- From: Geoff Keating <geoffk at geoffk dot org>
- To: Eric Botcazou <ebotcazou at libertysurf dot fr>
- Cc: gcc at gcc dot gnu dot org
- Date: 13 Sep 2003 15:35:24 -0700
- Subject: Re: Potential GC problem on the 3.3 branch
- References: <200309130637.02579.ebotcazou@libertysurf.fr>
Eric Botcazou <ebotcazou@libertysurf.fr> writes:
> Hi,
>
> I've come across a weird problem on the 3.3 branch with a big C++ file, which
> seems to be GC-related. A workaround is to slightly bump the default
> parameters of the GC.
>
> I'm not very familiar with the GC so I don't really know how to attack the
> problem. Could any GC specialist take a quick look when he has some time?
> (ok, I know, this is an oxymoron :-) I'd like to know whether it is really a
> GC problem and maybe have a few entry points to investigate.
>
> See http://gcc.gnu.org/PR12252
The best way to start investigating a GC problem is to use
--param ggc-min-heapsize=0 --param ggc-min-expand=0
which will force garbage collection to happen every time it can.
This should make the problem reproducible and make it easier to produce
a cut-down testcase.
> More generally, are GC problems safely fixable on a release branch?
Yes.
--
- Geoffrey Keating <geoffk@geoffk.org>