https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123886
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Richard Biener from comment #4) > I wonder > why this only shows up now, is it possible to bisect the issue? It might be because without release checking gc is set to a point where it happens at much higher rate and with -fsanitize=thread there is maybe more stuff in GC that would cause a GC to happen at the "wrong" time. and maybe with more IPA passes storing things out for LTO would have exposed it more often. So more likely just bad luck it showed up now vs before.
