public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/78915] missing -Wuninitialized accessing allocated memory
[not found] <bug-78915-4@http.gcc.gnu.org/bugzilla/>
@ 2021-04-01 20:58 ` msebor at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: msebor at gcc dot gnu.org @ 2021-04-01 20:58 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915
Martin Sebor <msebor at gcc dot gnu.org> 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 <msebor at gcc dot gnu.org> ---
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;
| ^~
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-04-01 20:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-78915-4@http.gcc.gnu.org/bugzilla/>
2021-04-01 20:58 ` [Bug middle-end/78915] missing -Wuninitialized accessing allocated memory msebor at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).