public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "justus at opentransactions dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107352] New: polymorphic class with destroying delete operator defined causes internal compiler error
Date: Fri, 21 Oct 2022 18:40:51 +0000	[thread overview]
Message-ID: <bug-107352-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107352
           Summary: polymorphic class with destroying delete operator
                    defined causes internal compiler error
           Product: gcc
           Version: 12.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: justus at opentransactions dot org
  Target Milestone: ---

Created attachment 53746
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53746&action=edit
build errors

Defining a std::destroying_delete_t operator delete for a polymorphic class
causes GCC to fail with "internal compiler error: in build_if_in_charge, at
cp/class.cc:229" 

I've tested with 10.3, 11.3, and 12.2 and all of them have the same issue. The
project both builds and passes tests successfully when compiled with clang and
the problem also goes away if I remove the destroying delete operator and put
the code that was in that function at all the places where it would have been
called.

             reply	other threads:[~2022-10-21 18:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 18:40 justus at opentransactions dot org [this message]
2022-10-21 18:41 ` [Bug c++/107352] " justus at opentransactions dot org
2022-10-21 18:41 ` justus at opentransactions dot org
2022-10-21 19:38 ` pinskia at gcc dot gnu.org
2022-10-21 19:52 ` justus at opentransactions dot org
2022-10-21 23:20 ` pinskia at gcc dot gnu.org
2022-10-21 23:25 ` 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-107352-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).