public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/93413] Defaulted constexpr Destructor not being found during constant evaluation Date: Thu, 03 Nov 2022 19:11:44 +0000 [thread overview] Message-ID: <bug-93413-4-DvM37hdkUb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93413-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93413 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED Target Milestone|--- |13.0 --- Comment #11 from Patrick Palka <ppalka at gcc dot gnu.org> --- Fixed for GCC 13. The fix is probably unsuitable for backporting, and there are workarounds anyway -- one workaround is to turn the problematic class into a class template with an explicitly defaulted dtor, e.g. for the original testcase do: struct Base { constexpr virtual ~Base(){} }; template<class=void> struct Derived: Base { ~Derived() = default; }; constexpr Derived<> d;
prev parent reply other threads:[~2022-11-03 19:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93413-4@http.gcc.gnu.org/bugzilla/> 2021-04-24 2:39 ` [Bug c++/93413] Destructor definition not " ldalessandro at gmail dot com 2021-08-17 5:56 ` pinskia at gcc dot gnu.org 2021-08-17 5:57 ` pinskia at gcc dot gnu.org 2021-08-17 5:58 ` pinskia at gcc dot gnu.org 2022-02-23 7:46 ` pinskia at gcc dot gnu.org 2022-07-13 22:44 ` pinskia at gcc dot gnu.org 2022-07-13 22:45 ` pinskia at gcc dot gnu.org 2022-11-02 20:39 ` pinskia at gcc dot gnu.org 2022-11-02 23:58 ` [Bug c++/93413] Defaulted constexpr Destructor not being " ppalka at gcc dot gnu.org 2022-11-03 18:56 ` cvs-commit at gcc dot gnu.org 2022-11-03 19:11 ` ppalka at gcc dot gnu.org [this message]
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-93413-4-DvM37hdkUb@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).