public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kacper.slominski72 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107512] New: Defaulted virtual destructor not considered in constexpr context
Date: Wed, 02 Nov 2022 20:36:24 +0000	[thread overview]
Message-ID: <bug-107512-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107512

            Bug ID: 107512
           Summary: Defaulted virtual destructor not considered in
                    constexpr context
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kacper.slominski72 at gmail dot com
  Target Milestone: ---

The following code causes a compiler error on GCC 12.2 and godbolt's trunk
(compiled with "-std=c++20 -Wall -Wextra -Wpedantic"):

struct base {
    constexpr virtual ~base() = default;
};

struct derived final : base {
    constexpr virtual ~derived() = default;
};

constexpr derived der;

The reported error is:

<source>:9:19: error: 'virtual constexpr derived::~derived()' used before its
definition
    9 | constexpr derived der;
      |                   ^~~

Changing the destructor to the following makes the error go away:

    constexpr virtual ~derived() { }

As does making the variable not constexpr. Clang seems to accept this without
any problems.

             reply	other threads:[~2022-11-02 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 20:36 kacper.slominski72 at gmail dot com [this message]
2022-11-02 20:39 ` [Bug c++/107512] " pinskia 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-107512-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: link
Be 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).