https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80147
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #2) > (In reply to Eric Gallager from comment #1) > > ...but if that's the case, then why doesn't the warning go away for i1, too? > > Because "is-used" is given before optimization, while may-be-used are given > after optimization. I don't think this is a bug, but expected behaviour > given that optimization should allow more precise warnings (hence, > discarding a false positive). It would be nice if we could avoid warning > about f1(i1), but that is hard with the current Wuninitialized > implementation (and a different already reported bug). Which other bug is that?
