public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52231] [missed optimization/diagnostics] address-of-reference
Date: Mon, 13 Feb 2012 18:19:00 -0000 [thread overview]
Message-ID: <bug-52231-4-joLRMm41E0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52231-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52231
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-13 18:19:39 UTC ---
(In reply to comment #1)
> References are just like pointers, just &a is really a and a is really *a.
This is wrong in so many ways.
Pointers can be null, pointers can be uninitialized, pointers can be re-seated.
Would you also argue this shouldn't be optimised?
int i=0;
int& r = i;
// ...
if (&i != &r)
unreachable();
next prev parent reply other threads:[~2012-02-13 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:33 [Bug c++/52231] New: " pluto at agmk dot net
2012-02-13 17:56 ` [Bug c++/52231] " pinskia at gcc dot gnu.org
2012-02-13 18:13 ` redi at gcc dot gnu.org
2012-02-13 18:19 ` redi at gcc dot gnu.org [this message]
2015-02-18 19:36 ` pinskia at gcc dot gnu.org
2015-02-18 19:44 ` froydnj at gcc dot gnu.org
2015-02-18 21:30 ` redi at gcc dot gnu.org
2015-02-18 22:04 ` froydnj 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-52231-4-joLRMm41E0@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).