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/63943] wrong location for -Wmaybe-uninitialized in inlined function
Date: Wed, 31 Mar 2021 16:15:04 +0000 [thread overview]
Message-ID: <bug-63943-4-7RXF2h7EHp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63943-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63943
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Last reconfirmed|2014-11-19 00:00:00 |2021-3-31
Known to fail|4.9.2, 5.0 |10.2.0, 11.0, 4.9.4, 5.5.0,
| |6.4.0, 7.2.0, 8.3.0, 9.1.0
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Reconfirmed with GCC 11 with mostly the same observations as in comment #1.
As for using %K, I mostly agree. I actually have %G in my tree, but my goal is
to get rid of both and replace them with a new warning function like so:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563862.html
and replace calls to warning() and warning_at() in the middle end with those to
the new function. This makes it possible to control warnings at any point in
the lining stack and resolves bug like pr98871.
next prev parent reply other threads:[~2021-03-31 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 23:01 [Bug c/63943] New: -Wmaybe-uninitialized pragma mishandled " eggert at gnu dot org
2014-11-19 15:16 ` [Bug middle-end/63943] wrong location for -Wmaybe-uninitialized " manu at gcc dot gnu.org
2021-03-31 16:15 ` msebor at gcc dot gnu.org [this message]
2021-03-31 17:56 ` manu at gcc dot gnu.org
2021-03-31 20:36 ` egallager at gcc dot gnu.org
2021-04-15 16:49 ` msebor 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-63943-4-7RXF2h7EHp@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).