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++/106213] -Werror=deprecated-copy-dtor does not trigger warning and error Date: Wed, 06 Jul 2022 20:42:43 +0000 [thread overview] Message-ID: <bug-106213-4-c1ZD24fsQB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106213-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106213 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=94492 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /* Don't warn if the flag was disabled around the class definition (c++/94492). */ if (warning_enabled_at (DECL_SOURCE_LOCATION (decl), OPT_Wdeprecated_copy)) { auto_diagnostic_group d; tree ctx = DECL_CONTEXT (decl); tree other = classtype_has_depr_implicit_copy (ctx); int opt = (DECL_DESTRUCTOR_P (other) ? OPT_Wdeprecated_copy_dtor : OPT_Wdeprecated_copy);
next prev parent reply other threads:[~2022-07-06 20:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-06 9:55 [Bug c++/106213] New: " federico.kircheis at gmail dot com 2022-07-06 20:41 ` [Bug c++/106213] " pinskia at gcc dot gnu.org 2022-07-06 20:42 ` pinskia at gcc dot gnu.org [this message] 2022-07-06 20:46 ` pinskia at gcc dot gnu.org 2023-12-19 20:42 ` jason at gcc dot gnu.org 2023-12-21 2:07 ` cvs-commit at gcc dot gnu.org 2023-12-21 21:59 ` 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-106213-4-c1ZD24fsQB@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).