https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78394
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #5) > Well, -Og doesn't do any of the detailed analysis and optimization that > would give the compiler the opportunity to eliminate the paths that result > in the false positive. So it's no great surprise. -O0 doesn't do any of that detailed analysis or optimization either, but it doesn't have the same issue of warning like -Og
