[Bug tree-optimization/18501] [6/7/8/9 Regression] Missing 'used uninitialized' warning (CCP)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 Jakub Jelinek changed: What|Removed |Added Target Milestone|6.5 |7.4 --- Comment #87 from Jakub Jelinek --- GCC 6 branch is being closed
[Bug tree-optimization/18501] [6/7/8/9 Regression] Missing 'used uninitialized' warning (CCP)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 Manuel López-Ibáñez changed: What|Removed |Added CC||gcc at cookiesoft dot de --- Comment #86 from Manuel López-Ibáñez --- *** Bug 87365 has been marked as a duplicate of this bug. ***
[Bug tree-optimization/18501] [6/7/8/9 Regression] Missing 'used uninitialized' warning (CCP)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 Manuel López-Ibáñez changed: What|Removed |Added CC||lvenkatakumarchakka at gmail dot c ||om --- Comment #85 from Manuel López-Ibáñez --- *** Bug 69578 has been marked as a duplicate of this bug. ***
[Bug tree-optimization/18501] [6/7/8/9 Regression] Missing 'used uninitialized' warning (CCP)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 Michael Veksler changed: What|Removed |Added CC||mickey.veksler at gmail dot com --- Comment #84 from Michael Veksler --- Ping. At least -Wmaybe-uninitialized should emit warnings. This still happens on the trunk (gcc version 9.0.0 20180723 (experimental) (GCC-Explorer-Build)) : int f(int a) { int ret; if (a) { ret = 1; } return ret; } No warning, including with -Wmaybe-uninitialized. All other compilers warn about this (at least clang and Visual C++).