https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120208
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- It is not exactly scan is the issue but what is assigned to scan. Both start and newstart are initialized conditionally. And it seems like it is hard to figure out if the conditions at which they are set are the same conditions we reach when assigning scan from start. Even myself has a hard time figuring it out if there is any path which either newstart or start is used uninitialized because it seems like it depends on the context of g->strip and more.
