public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106947] [12/13 Regression] -Waddress + bool + pragma generates meaningless diagnostic Date: Mon, 19 Sep 2022 18:41:52 +0000 [thread overview] Message-ID: <bug-106947-4-wQtXD0h0L2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106947-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106947 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:2d9429d5c0f86f588bdfd85bb9e236d2be367d3f commit r13-2723-g2d9429d5c0f86f588bdfd85bb9e236d2be367d3f Author: Marek Polacek <polacek@redhat.com> Date: Mon Sep 19 14:12:55 2022 -0400 c: Stray inform note with -Waddress [PR106947] A trivial fix for maybe_warn_for_null_address where we print an inform note without first checking the return value of a warning call. PR c/106947 gcc/c/ChangeLog: * c-typeck.cc (maybe_warn_for_null_address): Don't emit stray notes. gcc/testsuite/ChangeLog: * c-c++-common/Waddress-7.c: New test.
next prev parent reply other threads:[~2022-09-19 18:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-14 20:31 [Bug middle-end/106947] New: " eggert at cs dot ucla.edu 2022-09-14 20:39 ` [Bug c/106947] " pinskia at gcc dot gnu.org 2022-09-14 20:39 ` pinskia at gcc dot gnu.org 2022-09-14 20:42 ` [Bug c/106947] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-09-15 7:19 ` rguenth at gcc dot gnu.org 2022-09-15 15:19 ` mpolacek at gcc dot gnu.org 2022-09-19 18:41 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-19 18:43 ` cvs-commit at gcc dot gnu.org 2022-09-19 18:43 ` mpolacek at gcc dot gnu.org 2023-03-16 12:25 ` marxin 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-106947-4-wQtXD0h0L2@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).