This is the mail archive of the
mailing list for the GCC project.
Re: getting rid of ggc_push_context (was Re: Cleanup tree_rest_of_compilationinterface)
Jan Hubicka wrote:
Thanks.I would like to see ggc_push_context go away.
I wonder how desirable is to get rid of ggc_push_context/ggc_pop_context
machinery. It should not be terribly dificult deal to make cse.c ggc
safe but without using ggc_free that would bring other expenses.
What GGC guys prefer?
Clearly, because CSE generated a lot of garbage. I think that this
might have come from uses of the aliasing machinery which generated new
RTL constantly. In the abstract, there's no reason why CSE should be
generating lots of garbage in GC'd memory; it should only be generating
memory for (a) its hash tables, and (b) the new instructions it builds.
Perhaps it might be possible to trottle the cse memory consumption too.
Does someone recall why this call has been added?