public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thelordlucas at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98410] New: Default constructor generation fails on abstract class with virtual base Date: Mon, 21 Dec 2020 11:19:30 +0000 [thread overview] Message-ID: <bug-98410-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98410 Bug ID: 98410 Summary: Default constructor generation fails on abstract class with virtual base Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: thelordlucas at gmail dot com Target Milestone: --- Hi all, The following code fails to compile on GCC > 7: class Base { int x; public: Base(int x): x{x} {} virtual void f() = 0; }; class Derived : public virtual Base { public: Derived() = default; }; class Concrete: public Derived { public: Concrete(): Base{42} {} void f() override {} }; Link to code: https://godbolt.org/z/bn1EY6 It says that the Derived() constructor is deleted (error: use of deleted function 'Derived::Derived()'). Using Derived() {}; it compiles file. As the user eerorika points out in https://stackoverflow.com/questions/65287323/strange-default-empty-constructor-on-a-virtual-inheritance-behaviour-on-gcc the constructor Derived() should not have been deleted, since it is also abstract and doesn't fall in any default constructor deletion rule. Maybe related, it yielded "internal compiler error: in maybe_explain_implicit_delete, at cp/method.c:2671" if I add the noexcept to the deleted constructor: class Base { int x; public: Base(int x): x{x} {} virtual void f() = 0; }; class Derived : public virtual Base { public: Derived() noexcept = default; }; class Concrete: public Derived { public: Concrete(): Base{42} {} void f() override {} }; Link to code: https://godbolt.org/z/5fx8Ph I tested clang trunk, and it compiles both versions. Thanks!
next reply other threads:[~2020-12-21 11:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-21 11:19 thelordlucas at gmail dot com [this message] 2020-12-21 13:31 ` [Bug c++/98410] " marxin at gcc dot gnu.org 2022-05-23 9:35 ` redi 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-98410-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: 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).