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 middle-end/64568] [5 Regression] error: invalid reference prefix
Date: Mon, 12 Jan 2015 14:59:00 -0000 [thread overview]
Message-ID: <bug-64568-4-Ea2pmZ8d9D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64568-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64568
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Index: gcc/tree-ssa-forwprop.c
===================================================================
--- gcc/tree-ssa-forwprop.c (revision 219446)
+++ gcc/tree-ssa-forwprop.c (working copy)
@@ -2281,7 +2281,9 @@ pass_forwprop::execute (function *fun)
if (single_imm_use (lhs, &use_p, &use_stmt)
&& gimple_store_p (use_stmt)
&& !gimple_has_volatile_ops (use_stmt)
- && is_gimple_assign (use_stmt))
+ && is_gimple_assign (use_stmt)
+ && (TREE_CODE (gimple_assign_lhs (use_stmt))
+ != TARGET_MEM_REF))
{
tree use_lhs = gimple_assign_lhs (use_stmt);
tree new_lhs = build1 (REALPART_EXPR,
probably fixes it.
next prev parent reply other threads:[~2015-01-12 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 13:40 [Bug middle-end/64568] New: " trippels at gcc dot gnu.org
2015-01-12 14:56 ` [Bug middle-end/64568] " rguenth at gcc dot gnu.org
2015-01-12 14:59 ` rguenth at gcc dot gnu.org [this message]
2015-01-12 15:26 ` trippels at gcc dot gnu.org
2015-01-13 8:32 ` rguenth at gcc dot gnu.org
2015-01-13 8:32 ` rguenth at gcc dot gnu.org
2015-01-16 9:01 ` trippels at gcc dot gnu.org
2015-01-16 10:52 ` trippels at gcc dot gnu.org
2015-01-16 13:26 ` rguenth at gcc dot gnu.org
2015-01-16 15:50 ` trippels 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-64568-4-Ea2pmZ8d9D@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).