public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "leni536 at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111776] New: ICE on delete expression with multiple viable destroying operator delete Date: Wed, 11 Oct 2023 19:58:39 +0000 [thread overview] Message-ID: <bug-111776-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111776 Bug ID: 111776 Summary: ICE on delete expression with multiple viable destroying operator delete Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: leni536 at gmail dot com Target Milestone: --- version: gcc 13.2.0 flags: -std=c++20 -O2 -pedantic-errors ``` #include <memory> struct B { void operator delete(B* ptr, std::destroying_delete_t); }; struct D : B { void operator delete(D* ptr, std::destroying_delete_t); using B::operator delete; }; void bar(D* ptr) { delete ptr; } ``` internal compiler error: in build_op_delete_call, at cp/call.cc:7914 13 | delete ptr; | ^~~ 0x1ce7bde internal_error(char const*, ...) ???:0 0x7290fc fancy_abort(char const*, int, char const*) ???:0 0x7eb68c build_delete(unsigned int, tree_node*, tree_node*, special_function_kind, int, int, int) ???:0 0x7d3757 delete_sanity(unsigned int, tree_node*, tree_node*, bool, int, int) ???:0 0x89fd5b c_parse_file() ???:0 0x98c5d9 c_common_parse_file() ???:0 https://godbolt.org/z/8rh7h7EWz I'm not entirely sure what should actually happen here. I didn't find a disambiguating rule at https://timsong-cpp.github.io/cppwp/n4868/expr.delete#10 .
next reply other threads:[~2023-10-11 19:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-11 19:58 leni536 at gmail dot com [this message] 2023-10-11 20:08 ` [Bug c++/111776] " mpolacek at gcc dot gnu.org 2023-10-13 7:54 ` leni536 at gmail dot com 2023-11-15 10:37 ` leni536 at gmail dot com
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-111776-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).