This is the mail archive of the
mailing list for the GCC project.
Re: [tree-ssa PATCH] Pick memory consumption low hanging fruit
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Andrew MacLeod <amacleod at redhat dot com>
- Cc: Jeff Law <law at redhat dot com>, Steven Bosscher <s dot bosscher at student dot tudelft dot nl>, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 18 Nov 2003 17:50:33 -0500 (EST)
- Subject: Re: [tree-ssa PATCH] Pick memory consumption low hanging fruit
- References: <200311181955.hAIJtdwg001593@speedy.slc.redhat.com><1069194489.30703.332.camel@p4>
> Sigh. I dont suppose there would be a simple way to combine GC and a
> machanism for using GC memory, yet knowing when we are done with memory.
> When we get rid of a PHI node, we know we're done with it. It would be
> awful nice if we could say we're done with this, so it get put on a free
> list, and used the next time we need a PHI node. It seems silly to
> ignore this kind of information simply because we have agarbage
> colector that will figure it out for us.So have GC, and GC_free()..
The zone collector keeps free pages zone specific.
So if you had a phi node zone (or an ssa nodes zone), until it released
those pages (which happens if they weren't used last collection), they
would be reused only for the phi node/ssa nodes.