--- Additional Comments From dorit at il dot ibm dot com 2005-05-26 12:02
---
patch: http://gcc.gnu.org/ml/gcc-patches/2005-05/msg02477.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21639
--- Additional Comments From dorit at il dot ibm dot com 2005-05-24 15:16
---
(In reply to comment #7)
> > >So at the moment, you cannot run ggc_collect inside loop opts.
> > >
> > >
> > Is this going to change?
> >
> > If not, I guess removing TODO_ggc_collect is the simpliest thing
--- Additional Comments From rakdver at atrey dot karlin dot mff dot cuni
dot cz 2005-05-24 15:06 ---
Subject: Re: poisoned ggc memory used for -ftree-vectorize
> >there are several places in loop opts that are not GGC-safe (in
> >particular the tree nodes refered from loop structures
--- Additional Comments From paolo dot bonzini at lu dot unisi dot ch
2005-05-24 14:26 ---
Subject: Re: poisoned ggc memory used for -ftree-vectorize
>there are several places in loop opts that are not GGC-safe (in
>particular the tree nodes refered from loop structures are not
>seen
--- Additional Comments From rakdver at atrey dot karlin dot mff dot cuni
dot cz 2005-05-24 14:24 ---
Subject: Re: poisoned ggc memory used for -ftree-vectorize
> > Is there a rule that ggc_collect should not be called during loop
> optimizations?
>
> I don't know. (Zdenek?)
there a
--- Additional Comments From bonzini at gcc dot gnu dot org 2005-05-24
13:46 ---
scev_info_str should be ggc_alloc-ed.
Then, the hash table with the cache should be marked with GTY((param_is (struct
scev_info_str)))
If this fixes the bug, you can remove the TODO_ggc_collect from
lowe
--- Additional Comments From dorit at il dot ibm dot com 2005-05-24 12:54
---
> Is there a rule that ggc_collect should not be called during loop
optimizations?
I don't know. (Zdenek?)
I think passes within the loop optimizer can assume that the scev information
cached in the scev ht
--- Additional Comments From paolo dot bonzini at lu dot unisi dot ch
2005-05-24 11:59 ---
Subject: Re: poisoned ggc memory used for -ftree-vectorize
>Paolo, is the above solution ok with you? If so, I'll go ahead and prepare a
>patch. Alternatively, if ggc_collect is really required
--- Additional Comments From dorit at il dot ibm dot com 2005-05-24 11:53
---
I can reproduce this problem on powerpc-apple-darwin, even without the
options "-maltivec -mabi-altivec" (which means that no simd vectorization takes
place). What happens is that the scalar_evolution_info ha
