[Bug middle-end/78915] missing -Wuninitialized accessing allocated memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915 Martin Sebor changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|--- |11.0 Known to fail||10.2.0, 7.3.0, 8.3.0, 9.2.0 Status|NEW |RESOLVED --- Comment #4 from Martin Sebor --- Both f1() and f2() have been diagnosed since r11-959 (GCC 11): $ gcc -O1 -S -Wall pr78915.c pr78915.c: In function ‘f0’: pr78915.c:5:3: warning: ‘i’ is used uninitialized [-Wuninitialized] 5 | ++i; | ^~~ pr78915.c:3:7: note: ‘i’ was declared here 3 | int i; | ^ pr78915.c: In function ‘f1’: pr78915.c:14:5: warning: ‘*p’ is used uninitialized [-Wuninitialized] 14 | ++*p; | ^~ pr78915.c: In function ‘f2’: pr78915.c:25:5: warning: ‘*p’ may be used uninitialized [-Wmaybe-uninitialized] 25 | ++*p; | ^~
[Bug middle-end/78915] missing -Wuninitialized accessing allocated memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915 --- Comment #3 from Eric Gallager --- (In reply to Manuel López-Ibáñez from comment #2) > Possibly a dup of PR87209 Or vice versa.
[Bug middle-end/78915] missing -Wuninitialized accessing allocated memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915 Manuel López-Ibáñez changed: What|Removed |Added CC||manu at gcc dot gnu.org --- Comment #2 from Manuel López-Ibáñez --- Possibly a dup of PR87209
[Bug middle-end/78915] missing -Wuninitialized accessing allocated memory
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed||2017-08-28 CC||egallager at gcc dot gnu.org Blocks||24639 Ever confirmed|0 |1 --- Comment #1 from Eric Gallager --- Confirmed that only f0 warns. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639 [Bug 24639] [meta-bug] bug to track all Wuninitialized issues