public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60517] warning/error for taking address of member of a temporary object
Date: Sun, 06 Apr 2014 08:23:00 -0000 [thread overview]
Message-ID: <bug-60517-4-aMXRnLjyXM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60517-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60517
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #32549|0 |1
is obsolete| |
--- Comment #11 from Marc Glisse <glisse at gcc dot gnu.org> ---
Created attachment 32551
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32551&action=edit
first try
With clobber removal now.
It isn't so great, the statements before the clobber have already been removed
as dead code, so by removing the clobber we produce an uninitialized read for
which we get a warning later.
next prev parent reply other threads:[~2014-04-06 8:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:54 [Bug c++/60517] New: " manu at gcc dot gnu.org
2014-03-13 20:42 ` [Bug c++/60517] " glisse at gcc dot gnu.org
2014-03-13 23:44 ` manu at gcc dot gnu.org
2014-03-14 7:19 ` glisse at gcc dot gnu.org
2014-03-14 10:41 ` manu at gcc dot gnu.org
2014-03-14 12:13 ` glisse at gcc dot gnu.org
2014-03-14 15:41 ` glisse at gcc dot gnu.org
2014-03-14 16:51 ` manu at gcc dot gnu.org
2014-03-14 17:29 ` glisse at gcc dot gnu.org
2014-03-14 18:02 ` glisse at gcc dot gnu.org
2014-04-05 23:01 ` glisse at gcc dot gnu.org
2014-04-06 8:23 ` glisse at gcc dot gnu.org [this message]
2014-04-06 10:17 ` glisse at gcc dot gnu.org
2014-06-26 17:22 ` paolo.carlini at oracle dot com
2014-07-31 9:34 ` glisse at gcc dot gnu.org
2014-08-22 13:02 ` manu at gcc dot gnu.org
2014-08-22 13:22 ` glisse at gcc dot gnu.org
2014-11-22 14:48 ` glisse 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-60517-4-aMXRnLjyXM@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).