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] [10/11/12/13/14 Regression] wrong(?) devirtualization
Date: Tue, 09 May 2023 08:49:50 +0000 [thread overview]
Message-ID: <bug-109770-4-JYMPpMiVFQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109770-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109770
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to m.cencora from comment #6)
> (In reply to Richard Biener from comment #0)
> > #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).
>
> I believe you need to std::launder the p pointer before calling delete:
> https://en.cppreference.com/w/cpp/utility/launder
Ah, interesting. I was looking for an answer whether
new T
may produce anything other than an object with dynamic type T or if there
are any constraints on the object constructed. In particular C++20 11.10.4
refered to by 6.7.3 doesn't mention whether re-using the storage is
permitted for an object under construction. It says usage is limited
and doesn't explicitely allow re-use so that might mean re-use is not allowed.
Note std::launder is C++17 only, the original reporter was using C++98 / C++14
Reading C++20, 6.7.3/9, at least suggests that the placement new (this) A
in the CTOR invokes undefined behavior because the lifetime of B hasn't
ended (but 6.7.3/1.5 makes this ambiguous - we're re-using the storage here,
and also we're not talking about an object with automatic storage duration).
next prev parent reply other threads:[~2023-05-09 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 13:30 [Bug ipa/109770] New: " rguenth at gcc dot gnu.org
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 [this message]
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-JYMPpMiVFQ@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).