public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wmi at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64557] get_addr in true_dependence_1 cannot handle VALUE inside an expr
Date: Sat, 10 Jan 2015 21:47:00 -0000	[thread overview]
Message-ID: <bug-64557-4-fM1YjeE7VS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64557-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64557

--- Comment #1 from wmi at google dot com ---
The experimental patch is to call get_addr for VALUE of base before plus other
constant, when creating mem_addr for dependence check and for store_info.
bootstrap and regression on x86_64-linux-gnu are ok. 

Index: dse.c
===================================================================
--- dse.c    (revision 219421)
+++ dse.c    (working copy)
@@ -1564,6 +1564,7 @@ record_store (rtx body, bb_info_t bb_inf
         = rtx_group_vec[group_id];
       mem_addr = group->canon_base_addr;
     }
+      mem_addr = get_addr (mem_addr);
       if (offset)
     mem_addr = plus_constant (get_address_mode (mem), mem_addr, offset);
     }
@@ -2177,6 +2178,7 @@ check_mem_read_rtx (rtx *loc, bb_info_t
         = rtx_group_vec[group_id];
       mem_addr = group->canon_base_addr;
     }
+      mem_addr = get_addr (mem_addr);
       if (offset)
     mem_addr = plus_constant (get_address_mode (mem), mem_addr, offset);
     }


       reply	other threads:[~2015-01-10 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-64557-4@http.gcc.gnu.org/bugzilla/>
2015-01-10 21:47 ` wmi at google dot com [this message]
2015-01-10 22:07 ` ppluzhnikov at google dot com
2015-01-23 17:56 ` wmi at gcc dot gnu.org
2015-02-20 12:05 ` uros at gcc dot gnu.org
2015-02-20 12:06 ` ubizjak at gmail dot com
2015-10-15 10:41 ` vogt at linux dot vnet.ibm.com

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-64557-4-fM1YjeE7VS@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).