public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/40389] optimizer bug (possibly)
Date: Sun, 14 Jun 2009 15:42:00 -0000 [thread overview]
Message-ID: <20090614154202.12454.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40389-17817@http.gcc.gnu.org/bugzilla/>
------- Comment #25 from rguenther at suse dot de 2009-06-14 15:41 -------
Subject: Re: optimizer bug (possibly)
On Sun, 14 Jun 2009, jason at redhat dot com wrote:
> ------- Comment #23 from jason at redhat dot com 2009-06-14 15:39 -------
> Subject: Re: optimizer bug (possibly)
>
> On 06/13/2009 06:58 PM, rguenth at gcc dot gnu dot org wrote:
> > * gimple.c (walk_stmt_load_store_addr_ops): The LHS of a call
> > has its address taken if NRV was applied and it is addressable.
>
> This should check TREE_ADDRESSABLE on the type rather than the variable.
For what middle-end semantics? I check TREE_ADDRESSABLE to leave it
completely to the frontend if the LHS is addressable or not. So
the frontend should only set it if the type is TREE_ADDRESSABLE then.
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40389
next prev parent reply other threads:[~2009-06-14 15:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 15:46 [Bug c++/40389] New: " keesjan at cobalt dot et dot tudelft dot nl
2009-06-09 15:49 ` [Bug c++/40389] " keesjan at cobalt dot et dot tudelft dot nl
2009-06-09 17:11 ` jakub at gcc dot gnu dot org
2009-06-09 20:25 ` rguenth at gcc dot gnu dot org
2009-06-09 21:22 ` jakub at gcc dot gnu dot org
2009-06-09 21:27 ` rguenth at gcc dot gnu dot org
2009-06-09 21:31 ` pinskia at gcc dot gnu dot org
2009-06-09 21:44 ` jakub at gcc dot gnu dot org
2009-06-10 19:37 ` jason at gcc dot gnu dot org
2009-06-10 19:40 ` jason at gcc dot gnu dot org
2009-06-10 19:47 ` rguenth at gcc dot gnu dot org
2009-06-10 20:13 ` jason at gcc dot gnu dot org
2009-06-10 20:58 ` jason at gcc dot gnu dot org
2009-06-10 20:59 ` rguenth at gcc dot gnu dot org
2009-06-10 21:27 ` jakub at gcc dot gnu dot org
2009-06-10 21:28 ` jakub at gcc dot gnu dot org
2009-06-10 21:29 ` rguenth at gcc dot gnu dot org
2009-06-12 17:30 ` jason at redhat dot com
2009-06-12 18:58 ` jakub at gcc dot gnu dot org
2009-06-13 17:02 ` rguenth at gcc dot gnu dot org
2009-06-13 19:23 ` pinskia at gcc dot gnu dot org
2009-06-13 19:31 ` rguenth at gcc dot gnu dot org
2009-06-13 22:58 ` rguenth at gcc dot gnu dot org
2009-06-13 22:58 ` rguenth at gcc dot gnu dot org
2009-06-14 15:40 ` jason at redhat dot com
2009-06-14 15:40 ` jason at redhat dot com
2009-06-14 15:42 ` rguenther at suse dot de [this message]
2009-06-17 10:29 ` rguenth at gcc dot gnu dot org
2009-06-17 10:34 ` rguenth at gcc dot gnu dot org
2009-06-17 12:03 ` rguenth at gcc dot gnu dot org
2009-06-17 12:04 ` rguenth at gcc dot gnu dot 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=20090614154202.12454.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).