> htab_hash_pointer is fine if a hash table is never traversed, or such > traversal > can't affect code generation. E.g. graphite has some debug_* routines that > traverse such hash tables, that's fine, they aren't called at all during > compilation except for debugging sessions.
Ok, thanks for the detailed explanation. The two other htabs using htab_hash_pointer ivtype_map_elt_info and clast_name_index_elt_info are safe.