This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: [Bug tree-optimization/42641] Random code-generation differences with GRAPHITE
- From: Sebastian Pop <sebpop at gmail dot com>
- To: gcc-bugzilla at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 7 Jan 2010 15:29:45 -0600
- Subject: Re: [Bug tree-optimization/42641] Random code-generation differences with GRAPHITE
- References: <bug-42641-10053@http.gcc.gnu.org/bugzilla/> <20100107211016.15260.qmail@sourceware.org>
> 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.