This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] Move loop structures to gc memory
On May 18, 2007, "Daniel Berlin" <dberlin@dberlin.org> wrote:
> On 5/18/07, Alexandre Oliva <aoliva@redhat.com> wrote:
>> Why is it not suitable?
> Because it's garbage collected memory for something that doesn't need
> to, care about, or will ever be, garbage collected?
> the memory doesn't need to be garbage collected, it just has some
> roots in it.
Do you not realize the contradiction between your two statements
above?
It evidently cares about garbage collection, because it points to
GC-able objects.
> Why should things that don't need to be garbage collected, be in
> garbage collected memory?
They don't have to. But they can. It's the logical nonsequitur that
"GC is unsuitable" that I'm disputing.
I have no qualms whatsoever about moving it out of GC right now, even
more so after I learned how hard it was to try to get incremental
speedups to the current implementation.
But I do take issue with the general claim that GC memory in general
is unsuitable for this, or any, purpose.
>> If we could make ggc_alloc faster, would it still be unsuitable?
This was the critial question. And, in spite of all of your
reasoning, it was left unanswered.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}