https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70647
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |manu at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Matt Godbolt from comment #0)
> In the move case, there's no such warning. I appreciate this is probably
> difficult (if not impossible) to detect, but if there's any way it can be
> done, it would save a painful debugging session or two!
I don't think "move" has anything to do with this. If you use "a + 1" or
"foo(a)", you are still initializing "a" with an uninitialized value.
In that sense, this is what PR19808 is about, for which there is a patch but,
sadly, nobody has had so far the time or interest to finish it and properly
submit it.
*** This bug has been marked as a duplicate of bug 19808 ***
