https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92757
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- >is too general and important a piece of information to be buried in the >documentation of individual warning flags. Yes because you should read the whole documentation rather than bits and pieces of it. When a warning is outputted, the option the warning is associated with is also outputted and so you could go and read about that specific option to find information about if the warning is effected by optimization or not
