public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/99959] [9/10/11 Regression] missing -Wuninitialized for an esra variable with TREE_NO_WARNING
Date: Wed, 07 Apr 2021 15:10:00 +0000 [thread overview]
Message-ID: <bug-99959-4-LkhCbXPeEX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99959-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99959
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|missing -Wuninitialized for |[9/10/11 Regression]
|an esra variable with |missing -Wuninitialized for
|TREE_NO_WARNING |an esra variable with
| |TREE_NO_WARNING
Keywords| |diagnostic
Known to fail| |10.2.0, 11.0, 6.3.0, 7.0.1,
| |8.3.0, 9.3.0
Blocks| |24639
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning has been suppressed since r230968 (6.0.0 20151126). Until then,
GCC issued:
pr99959.c:7:5: warning: ‘FRAME.0.i’ is used uninitialized in this function
[-Wuninitialized]
__builtin_printf ("%i", i); // missing -Wuninitialized
^~~~~~~~~~~~~~~~~~~~~~~~~~
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
[Bug 24639] [meta-bug] bug to track all Wuninitialized issues
next prev parent reply other threads:[~2021-04-07 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 14:58 [Bug middle-end/99959] New: " msebor at gcc dot gnu.org
2021-04-07 15:10 ` msebor at gcc dot gnu.org [this message]
2021-04-08 7:07 ` [Bug middle-end/99959] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-04-08 14:23 ` rguenth at gcc dot gnu.org
2021-06-01 8:20 ` [Bug middle-end/99959] [9/10/11/12 " rguenth at gcc dot gnu.org
2021-06-26 15:16 ` egallager at gcc dot gnu.org
2021-06-28 20:08 ` msebor at gcc dot gnu.org
2022-05-27 9:44 ` [Bug middle-end/99959] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2023-07-07 10:39 ` [Bug middle-end/99959] [11/12/13/14 " rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99959-4-LkhCbXPeEX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).