https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107138
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Marco Clemencic from comment #8) > But the warning is not issued in -O0 builds, which I believe means the code > is correct by itself, That's not a valid assumption. -Wmaybe-uninitialized doesn't even run for -O0 so you won't get those warnings even for incorrect code. So you can't infer anything from the absence of such warnings with -O0.
