This is the mail archive of the
mailing list for the GCC project.
Re: [tree-ssa] Memory usage in compute_immediate_uses
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Jeff Law <law at redhat dot com>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, Daniel Jacobowitz <drow at mvista dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Tue, 16 Sep 2003 16:52:53 -0400
- Subject: Re: [tree-ssa] Memory usage in compute_immediate_uses
- Organization: Red Hat Canada
- References: <200309162044.h8GKiOEg010884@speedy.slc.redhat.com>
On Tue, 2003-09-16 at 16:44, email@example.com wrote:
> In message <firstname.lastname@example.org>, Diego Novillo w
> >On Tue, 2003-09-16 at 16:26, Daniel Berlin wrote:
> >> On Tue, 16 Sep 2003, Diego Novillo wrote:
> >> > Another thing we could use is ggc_collect() after each pass through
> >> > optimize_function_tree().
> >> Have you tried to see if this works right now?
> >Yup. The other day, when I ran into that GC problem with the vops
> >varrays, I had it collecting after every single pass. It seemed to
> Hey -- want to comment on this? Is whatever fix you came up with in
> the tree already?
Yes. I committed it about 10 days ago.
It amounted to not lying to GC with the voperand arrays. Now that I
read my posting again, I really didn't comment on the problem I was
having. Essentially the call to ggc_collect() done inside PRE was
zapping virtual operands that we were actually still using. The problem
went away with this patch:
I was the only one having that problem. At the time I thought it was
something I was messing up with other patches I had in my tree.