public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Question on load motion in GCSE
@ 2012-10-30 13:47 Bin.Cheng
  2012-10-30 15:55 ` Bin.Cheng
  0 siblings, 1 reply; 2+ messages in thread
From: Bin.Cheng @ 2012-10-30 13:47 UTC (permalink / raw)
  To: gcc

Hi,
When doing load motion in GCSE, it depends on different simple memory
refers in pre_ldst_table won't clobber(alias to) each other.
I am assuming function simple_mem is the answer to this question, but
what I don't understand is how simple_mem can make sure of this?

Did I understand the load motion in a wrong way? Please help. Thanks.

-- 
Best Regards.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Question on load motion in GCSE
  2012-10-30 13:47 Question on load motion in GCSE Bin.Cheng
@ 2012-10-30 15:55 ` Bin.Cheng
  0 siblings, 0 replies; 2+ messages in thread
From: Bin.Cheng @ 2012-10-30 15:55 UTC (permalink / raw)
  To: gcc

On Tue, Oct 30, 2012 at 9:47 PM, Bin.Cheng <amker.cheng@gmail.com> wrote:
> Hi,
> When doing load motion in GCSE, it depends on different simple memory
> refers in pre_ldst_table won't clobber(alias to) each other.
> I am assuming function simple_mem is the answer to this question, but
> what I don't understand is how simple_mem can make sure of this?
>
> Did I understand the load motion in a wrong way? Please help. Thanks.
>
Please ignore this message. I just realized that GCC retreats to
normal alias information in mems_conflict_for_gcse_p function for
different memory refs in pre_ldst_table.


-- 
Best Regards.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-10-30 15:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-10-30 13:47 Question on load motion in GCSE Bin.Cheng
2012-10-30 15:55 ` Bin.Cheng

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).