https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79768
--- Comment #4 from Casper Ti. Vector ---
(In reply to Manuel López-Ibáñez from comment #3)
> This is just too weird code for GCC to analyze correctly at -O2. It doesn't
> warn at -O3 (with 5.4.0 20160609)
The coding pattern is quite common
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79768
--- Comment #2 from Casper Ti. Vector ---
Created attachment 40856
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40856=edit
Output of `sed '/^#/d; /^[ \t]*$/d' < gcc_bug.i'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79768
--- Comment #1 from Casper Ti. Vector ---
Created attachment 40855
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40855=edit
Output of `gcc -v -save-temps -Wall -O2 -c gcc_bug.c -o gcc_bug.o'
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: caspervector at gmail dot com
Target Milestone: ---
The following source file (here called `gcc_bug.c') triggers
`-Wmaybe-uninitialized' when compiled with `-Os', `-O1' or stronger
