public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109740] -Woverloaded-virtual is too aggressive Date: Thu, 04 May 2023 16:46:26 +0000 [thread overview] Message-ID: <bug-109740-4-mDaXzaAf3P@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109740-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109740 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The warning is specifically designed this way and even is documented to warn. https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/C_002b_002b-Dialect-Options.html#index-Woverloaded-virtual It is designed this way so you don't accidently have the wrong arguments (types and/or count). The documentation even talks about that: "In cases where the different signatures are not an accident,"
next prev parent reply other threads:[~2023-05-04 16:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 16:40 [Bug c++/109740] New: " psmith at gnu dot org 2023-05-04 16:46 ` pinskia at gcc dot gnu.org [this message] 2023-05-04 17:45 ` [Bug c++/109740] " psmith at gnu dot org 2023-11-01 18:04 ` emerg.reanimator at gmail dot com 2023-11-01 18:56 ` emerg.reanimator at gmail dot com 2023-11-02 20:52 ` emerg.reanimator at gmail dot com
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-109740-4-mDaXzaAf3P@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).