[Bug tree-optimization/107838] spurious "may be used uninitialized" warning on variable initialized at the first iteration of a loop

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107838

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
comment#3 is a slightly different issue in that we do not have the guarding
condition obviously true here, instead what we'd need to prove is that
r_8 is always initialized because the first loop iteration initializes it.

Maybe it's somehow possible to code that into the uninit analysis machinery,
I'd have to think about this.