https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108697
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- 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?
