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] [11/12/13/14 Regression] wrong(?) devirtualization
Date: Fri, 12 Jan 2024 10:53:54 +0000 [thread overview]
Message-ID: <bug-109770-4-na8pednhzg@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #9)
> (In reply to Richard Biener from comment #0)
> > Base *p = new B;
>
> I think if there isn't really a B at this address, then the derived-to-base
> conversion would be undefined.
>
> So on that basis, the compiler should be allowed to assume that there really
> is a B there.
OK, that makes sense.
prev parent reply other threads:[~2024-01-12 10:53 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
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 [this message]
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-na8pednhzg@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).