https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87315
--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Martin Sebor from comment #4) > To be clear: besides the missing warning this is also about the kind of code > GCC emits for the uninitialized read -- a missed-optimization for lack of a > better term/keyword. It would be safer to do what Clang does and either > replace the code with a trap, or simply eliminate it altogether. Bug 87209 > only covers the missing warning aspect. If you think it is more useful, please mark the other as a duplicate of this one. Or change the title of the other one. I used the other one as the main one because Richard pointed out where to look at to solve it.