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/103036] incorrect #pragma GCC diagnostic suppression for macro expansion and -Wuninitialized Date: Mon, 01 Nov 2021 23:53:40 +0000 [thread overview] Message-ID: <bug-103036-4-45k3sZSpuh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103036-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103036 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |diagnostic Blocks| |24639 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=90400 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- See also pr90400 which is about using a _Pragma to suppress -Wmaybe-uninitialized in macros. Removing the linemap_resolve_location() calls from tree-ssa-uninit.c isn't enough to fix that bug but it's prerequisite for a consistent behavior for the suppression of all warnings. 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-11-01 23:53 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-01 23:50 [Bug middle-end/103036] New: " msebor at gcc dot gnu.org 2021-11-01 23:53 ` msebor at gcc dot gnu.org [this message] 2022-10-04 1:58 ` [Bug middle-end/103036] " lhyatt 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-103036-4-45k3sZSpuh@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: linkBe 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).