public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "duyuehai at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/50955] [4.7 Regression] IVopts incorrectly rewrite the address of a global memory access into a local form.
Date: Thu, 03 Nov 2011 06:25:00 -0000	[thread overview]
Message-ID: <bug-50955-4-DOPp3s8n6l@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50955-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50955

--- Comment #6 from Yuehai Du <duyuehai at gmail dot com> 2011-11-03 06:24:58 UTC ---
Let me see if i understand you correctly, you are saying that there isn't an
easy way to fix it without hurting the performance(either consider less IV
candidates or dumb down the alias analysis). 
 so this issue won't be fixed  in trunk now?
if in that case, Avoiding the issue by set PARM isn't an option for me.  i
still want to fix it in our private port even with an ugly patch. can we just
add a new field in MEM_REF which specify it is local or non-nolocal
store(enum{INVALID, LOCAL, NON-LOCAL}),  and only set it in IVOPTS before it
rewrite the address. we will check this in is_hidden_global_store(). do this
work in Gimple level? but i don't know if RTL optimization still delete this
store because we don't keep points-to information.


  parent reply	other threads:[~2011-11-03  6:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  5:12 [Bug tree-optimization/50955] New: " duyuehai at gmail dot com
2011-11-02  5:19 ` [Bug tree-optimization/50955] " duyuehai at gmail dot com
2011-11-02  9:42 ` [Bug tree-optimization/50955] [4.7 Regression] " rguenth at gcc dot gnu.org
2011-11-02 12:50 ` rguenth at gcc dot gnu.org
2011-11-02 13:10 ` rguenth at gcc dot gnu.org
2011-11-02 13:33 ` rguenth at gcc dot gnu.org
2011-11-03  6:25 ` duyuehai at gmail dot com [this message]
2011-11-03  7:52 ` rguenther at suse dot de
2011-11-03  8:07 ` rakdver at kam dot mff.cuni.cz
2011-11-03  8:19 ` rguenth at gcc dot gnu.org
2011-12-06 13:56 ` rguenth at gcc dot gnu.org
2012-01-31 10:51 ` rguenth at gcc dot gnu.org
2012-01-31 14:24 ` rguenth at gcc dot gnu.org
2012-02-06 13:43 ` rguenth at gcc dot gnu.org
2012-02-06 13:44 ` rguenth at gcc dot gnu.org
2013-08-16  4:19 ` pinskia at gcc dot gnu.org
2013-08-16  7:02 ` pinskia at gcc dot gnu.org
2013-08-28  8:33 ` rguenther at suse dot de
2013-12-18  9:42 ` rguenther at suse dot de
2013-12-18 10:24 ` amker.cheng at gmail dot com
2013-12-19  9:57 ` rguenth at gcc dot gnu.org
2015-08-28  9:16 ` amker 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-50955-4-DOPp3s8n6l@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).