[patch] Move loop structures to gc memory

[Ian Lance Taylor]

Daniel Jacobowitz <drow@false.org> writes:

> On Mon, May 14, 2007 at 02:26:39PM -0700, Ian Lance Taylor wrote:
> > Using ggc_free with GC just puts us on the road back to the problems
> > which led us to introduce GC in the first place: we didn't track our
> > memory allocations properly, so we got confused and got weird crashes.
> 
> That's no more true than it would be if we used malloc instead for any
> particular allocation.  We have lots of allocation strategies in
> today's GCC (whether that's a good thing or not); I think "GC with
> explicit death marking" is just as valid as "plain GC".

We have different allocation strategies for different reasons.

Why do we need the strategy of "GC with explicit death marking?"  What
goal does that serve?

Except to work around a bug in our GC implementation?  And in that
case, why not fix the bug?

Ian