public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45221] missed optimization with multiple bases and casting
Date: Sat, 07 Aug 2010 16:27:00 -0000 [thread overview]
Message-ID: <20100807162740.31347.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45221-17658@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from rguenth at gcc dot gnu dot org 2010-08-07 16:27 -------
(In reply to comment #7)
> Richard, if you can't derive non-NULL-ness from X& y = *x, how do foo3 and fooB
> avoid the null check?
For both cases the C++ frontend do not emit the NULL check.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45221
next prev parent reply other threads:[~2010-08-07 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 1:28 [Bug c++/45221] New: missed optimization on casting pointers even under -O3 navin dot kumar at gmail dot com
2010-08-07 1:29 ` [Bug c++/45221] " navin dot kumar at gmail dot com
2010-08-07 1:33 ` [Bug c++/45221] missed optimization with multiple bases and up casting and dereferencing pinskia at gcc dot gnu dot org
2010-08-07 2:27 ` navin dot kumar at gmail dot com
2010-08-07 10:37 ` [Bug c++/45221] missed optimization with multiple bases and casting rguenth at gcc dot gnu dot org
2010-08-07 15:26 ` navin dot kumar at gmail dot com
2010-08-07 16:19 ` rguenth at gcc dot gnu dot org
2010-08-07 16:23 ` navin dot kumar at gmail dot com
2010-08-07 16:25 ` rguenth at gcc dot gnu dot org
2010-08-07 16:27 ` rguenth at gcc dot gnu dot org [this message]
2010-08-07 17:28 ` navin dot kumar at gmail dot com
[not found] <bug-45221-4@http.gcc.gnu.org/bugzilla/>
2011-05-17 15:49 ` navin.kumar at gmail dot com
2023-05-06 18:14 ` 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=20100807162740.31347.qmail@sourceware.org \
--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).