public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96876] New: missing check for destructibility of base classes in aggregate initialization
Date: Mon, 31 Aug 2020 20:53:08 +0000	[thread overview]
Message-ID: <bug-96876-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96876
           Summary: missing check for destructibility of base classes in
                    aggregate initialization
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: richard-gccbugzilla at metafoo dot co.uk
  Target Milestone: ---

GCC accepts this invalid code (which is ill-formed because [dcl.init.aggr]/8
says it potentially-invokes the destructor for B, which [class.dtor]/15 says
requires the destructor to be accessible):

struct B {
protected:
    ~B() {}
};

struct C : B { int n; };

int f();

void g() {
    C c{{}, f()};
}

... and generates wrong code for this similar example:

#include <stdio.h>

struct B {
public:
    ~B() { puts("destroyed"); }
};

struct C : B { int n; };

int f() { throw "hello"; }

int main() {
    try {
    C c{{}, f()};
    } catch (const char*) {
    }
}

... which is required to print "destroyed" (when the B base class subobject is
destroyed during stack unwinding), but with GCC does not.

             reply	other threads:[~2020-08-31 20:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 20:53 richard-gccbugzilla at metafoo dot co.uk [this message]
2020-08-31 22:29 ` [Bug c++/96876] " mpolacek at gcc dot gnu.org
2022-01-28  4:42 ` jason at gcc dot gnu.org
2022-02-09  1:10 ` cvs-commit at gcc dot gnu.org
2022-02-09  1:12 ` 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-96876-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).