PATCH for type hash-table

Richard Kenner kenner@vlsi1.ultra.nyu.edu
Tue Aug 31 22:41:00 GMT 1999


    Yes, that can happen, but that's not the case here.  I've got a
    situation where I really want the saveable_obstack to be the
    permanent_obstack, but I *don't* want the current_obstack to be the
    permanent_obstack.  Thus, the *type* (and all of its sub-components)
    are permanent, but the *entry* in the hash-table is not permanent.

Ah, so perhaps the call should be to savealloc?

    But what's the point?  Surely it makes sense that things that are
    going to live forever (the hash-table entries) be permanent?

True, I suppose.  I guess it doesn't hurt, but my feeling is that so
long as changes are being made here, things might as well be tightened
up at the same time.



More information about the Gcc-patches mailing list