This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/42641] Random code-generation differences with GRAPHITE
- From: "sebpop at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Jan 2010 21:30:17 -0000
- Subject: [Bug tree-optimization/42641] Random code-generation differences with GRAPHITE
- References: <bug-42641-10053@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #9 from sebpop at gmail dot com 2010-01-07 21:30 -------
Subject: Re: Random code-generation differences
with GRAPHITE
> 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.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42641