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++/99251] [11 Regression] inconsistent -Wnonnull warning behaviour with dynamic_cast
Date: Tue, 02 Mar 2021 18:17:34 +0000	[thread overview]
Message-ID: <bug-99251-4-3hVl8yMPUE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99251-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99251

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:

https://gcc.gnu.org/g:66ecb059c9d77cfcfb06cbdc3cac6a63b9e67f3d

commit r11-7458-g66ecb059c9d77cfcfb06cbdc3cac6a63b9e67f3d
Author: Martin Sebor <msebor@redhat.com>
Date:   Tue Mar 2 11:12:50 2021 -0700

    PR c++/99251 - inconsistent -Wnonnull warning behaviour with dynamic_cast

    gcc/cp/ChangeLog:

            PR c++/99251
            * class.c (build_base_path): Call build_if_nonnull.
            * cp-tree.h (build_if_nonnull): Declare.
            * rtti.c (ifnonnull): Rename...
            (build_if_nonnull): ...to this.  Set no-warning bit on COND_EXPR.
            (build_dynamic_cast_1): Adjust to name change.

    gcc/testsuite/ChangeLog:

            PR c++/99251
            * g++.dg/warn/Wnonnull9.C: Expect no warnings.
            * g++.dg/warn/Wnonnull12.C: New test.

  parent reply	other threads:[~2021-03-02 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 16:21 [Bug c++/99251] New: Strange " sirl at gcc dot gnu.org
2021-02-24 17:12 ` [Bug c++/99251] [11 Regression] inconsistent " msebor at gcc dot gnu.org
2021-02-24 17:13 ` msebor at gcc dot gnu.org
2021-02-24 18:14 ` msebor at gcc dot gnu.org
2021-02-24 22:29 ` msebor at gcc dot gnu.org
2021-02-25  7:59 ` rguenth at gcc dot gnu.org
2021-03-02 18:17 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-02 18:18 ` msebor at gcc dot gnu.org
2021-06-28 20:13 ` 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-99251-4-3hVl8yMPUE@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).