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++/87729] Please include -Woverloaded-virtual in -Wall Date: Thu, 07 Jul 2022 16:00:20 +0000 [thread overview] Message-ID: <bug-87729-4-7AQzHndBZ6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-87729-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87729 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:81bec060e31b6ef2feeb3046c6f13a207c6f698a commit r13-1559-g81bec060e31b6ef2feeb3046c6f13a207c6f698a Author: Jason Merrill <jason@redhat.com> Date: Thu Jul 7 10:12:04 2022 -0400 c++: -Woverloaded-virtual and dtors [PR87729] My earlier patch broke out of the loop over base members when we found a match, but that caused trouble for dtors, which can have multiple for which same_signature_p is true. But as the function comment says, we know this doesn't apply to [cd]tors, so skip them. PR c++/87729 gcc/cp/ChangeLog: * class.cc (warn_hidden): Ignore [cd]tors. gcc/testsuite/ChangeLog: * g++.dg/warn/Woverloaded-virt3.C: New test.
next prev parent reply other threads:[~2022-07-07 16:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-87729-4@http.gcc.gnu.org/bugzilla/> 2020-08-07 14:48 ` xantares09 at hotmail dot com 2020-08-07 14:49 ` xantares09 at hotmail dot com 2020-09-21 0:04 ` egallager at gcc dot gnu.org 2022-06-24 19:34 ` jason at gcc dot gnu.org 2022-06-24 21:29 ` dblaikie at gmail dot com 2022-06-24 22:26 ` cvs-commit at gcc dot gnu.org 2022-06-24 22:28 ` jason at gcc dot gnu.org 2022-07-05 8:17 ` sbergman at redhat dot com 2022-07-07 16:00 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-08 6:11 ` sbergman at redhat dot com 2022-07-25 13:23 ` cvs-commit at gcc dot gnu.org 2022-07-25 13:24 ` jason 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-87729-4-7AQzHndBZ6@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).