https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #5 from Aldy Hernandez <aldyh at gcc dot gnu.org> --- (In reply to Richard Biener from comment #3) > But yes, your observation about m_has_cache_entry is correct - if that has > any value (it makes reset_path "cheap"), then it should be also relied on > upon > growth. Maybe make this bitmap an optional feature of the cache itself > and handle it transparently there? BTW, if putting the bitmap in the ssa_global_cache itself works, that's fine as well, especially if it makes the ranger's cache faster :).
