public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sirl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99251] New: Strange -Wnonnull warning behaviour with dynamic_cast Date: Wed, 24 Feb 2021 16:21:40 +0000 [thread overview] Message-ID: <bug-99251-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99251 Bug ID: 99251 Summary: Strange -Wnonnull warning behaviour with dynamic_cast Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: sirl at gcc dot gnu.org Target Milestone: --- With this testcase: class cl1 { virtual void m(); }; class cl2 : public cl1 { public: int g(); int h(); int i(); }; class cl3 { cl1 *p; int g(); int h(); int i(); }; int cl3::g() { if (!p) return 0; cl2 *x = dynamic_cast<cl2 *>(p); return x->g(); } int cl3::h() { if (!p) return 0; return (dynamic_cast<cl2 *>(p))->h(); } int cl3::i() { if (!p) return 0; return dynamic_cast<cl2 *>(p)->i(); } compiled with g++-trunk@r11-7356 -Wnonnull this warning is issued: testcase.cpp: In member function 'int cl3::i()': testcase.cpp:30:36: warning: 'this' pointer is null [-Wnonnull] 30 | return dynamic_cast<cl2 *>(p)->i(); | ^ testcase.cpp:8:7: note: in a call to non-static member function 'int cl2::i()' 8 | int i(); | ^ I believe there should be no warning for cl3::i() like with g++-10.2.
next reply other threads:[~2021-02-24 16:21 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-24 16:21 sirl at gcc dot gnu.org [this message] 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 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@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).