https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97292
--- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> --- And is it again the operator++ triggering the problem? It looks like aliasing bug to me, but in a template hell and -Wstrict-aliasing=3 is happy. The reason why parameter tracking is necessary seems to be the fact that we figure out some accesses from inner calls are local to the ++ operator and do not consider them in a summary (that is correct)
