https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108432
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Many warning messages are also dependent on optimisation level. And the
actual generated code is as well ;-)
-O0 means do the least possible work to generate correct code. There is
friction between that and having -fanalyzer do deep inspection of the code.
I think we should document -fanalyzer needs some optimisation enabled (does
it need -O2 in some cases, or just -O1 always, btw?)
The suggestion to at least check the last loop iteration is good of course.
