Problem with libiberty's hash tables

[Paolo Bonzini]

>  The structures left at the end
> (which correspond to memory leaks) are then displayed to allow the
> user to fix his leaks. The CPU usage is probably the limiting factor,
> here, as I want to avoid slowing the program down more than necessary.

Sure it's faster this way, but what's wrong with valgrind? ;-)

> I guess that, because I need to delete entries, the pointer_map
> wouldn't work, is that right? Plus, pointer_map is not library code...

What do you mean, is not library code?  Do you need it in libgfortran or 
in GCC?

If the latter, of course you could write pointer_map_delete yourself; it 
might be worthwhile since pointer maps are a tad faster than libiberty 
hashtabs.  It's on my todo list, but I wrote pointer_map for my private 
work on gcc and it was not needed at the time.

Paolo