On Tue, Jun 11, 2013 at 7:07 AM, shmeel gutl
shmeelg...@shmuelhome.mine.nu wrote:
In the architecture that I am using, there is a big pipeline penalty for
read after write to the same memory location. Is it possible to tell the
difference between a possible memory conflict and a definite memory
In the architecture that I am using, there is a big pipeline penalty for
read after write to the same memory location. Is it possible to tell the
difference between a possible memory conflict and a definite memory
conflict?
Hello,
better do
else if (!mem_read_insn_p (to-insn))
+ create_ddg_dep_no_link (g, from, to, ANTI_DEP, MEM_DEP, 0);
+ }
Done. Committed to -r175090.
Thanks,
Revital
Revital Eres revital.e...@linaro.org wrote on 13/06/2011 10:29:06 AM:
From: Revital Eres revital.e...@linaro.org
To: Ayal Zaks/Haifa/IBM@IBMIL
Cc: gcc-patches@gcc.gnu.org, Patch Tracking patc...@linaro.org
Date: 13/06/2011 10:29 AM
Subject: [PATCH, SMS] Fix violation of memory dependence
Hello,
The attached patch fixes violation of memory dependencies. The
problematic scenario happens when -fmodulo-sched-allow-regmoves flag
is set and certain anti-dep edges are not created.
For example, consider the following three instructions and the edges
between them. When
