public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/109770] New: wrong(?) devirtualization Date: Mon, 08 May 2023 13:30:29 +0000 [thread overview] Message-ID: <bug-109770-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109770 Bug ID: 109770 Summary: wrong(?) devirtualization Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: rguenth at gcc dot gnu.org CC: marxin at gcc dot gnu.org Target Milestone: --- #include <new> struct Base { virtual ~Base() {} }; struct A : Base { virtual ~A() {} }; struct B : Base { [[gnu::noinline]] B() { new (this) A; } virtual ~B() { __builtin_abort (); } }; int main() { Base *p = new B; delete p; } aborts when compiled with -O2 (with devirtualization enabled). Neither GCC nor clang diagnose the placement new in B::B() (but it looks fishy).
next reply other threads:[~2023-05-08 13:30 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 13:30 rguenth at gcc dot gnu.org [this message] 2023-05-08 13:31 ` [Bug ipa/109770] " rguenth at gcc dot gnu.org 2023-05-08 13:34 ` rguenth at gcc dot gnu.org 2023-05-08 17:09 ` rguenth at gcc dot gnu.org 2023-05-08 17:14 ` [Bug ipa/109770] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-05-08 17:21 ` [Bug ipa/109770] [10/11/12/13/14 " rguenth at gcc dot gnu.org 2023-05-09 8:24 ` m.cencora at gmail dot com 2023-05-09 8:49 ` rguenth at gcc dot gnu.org 2023-05-09 9:34 ` m.cencora at gmail dot com 2023-05-17 17:07 ` redi at gcc dot gnu.org 2023-07-07 10:45 ` [Bug ipa/109770] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-01-12 10:53 ` rguenth 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-109770-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).