This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Adding ggc_free to htab_create_ggc macro?
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Daniel Berlin <dberlin at dberlin dot org>
- Cc: gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Fri, 26 Mar 2004 00:42:38 -0800
- Subject: Re: Adding ggc_free to htab_create_ggc macro?
- References: <1A65180E-7EE4-11D8-9E31-000A95DA505C@dberlin.org>
Daniel Berlin <dberlin@dberlin.org> writes:
> Now that we have a ggc_free, should we use it in our htab_create_ggc
> macro as the htab_free.
> I'm not talking about the htab_delete function, I mean the last
> argument, which controls what the table itself is allocated/freed
> what, not the entries.
> That would let the htab free the old ggc_alloc'd memory immediately
> when it expands the table.
> We use htab_create_ggc in quite a few places, so it seems like it
> might be a win.
> Has anyone benchmarked this change, and found it to be a loss, or was
> this just not explored yet?
Not explored yet.
zw