Displaying 3 results from an estimated 3 matches for "recordload".
2014 Dec 11
2
[LLVMdev] dynamic data dependence extraction using llvm
...ue or false.
Since I can not distinguish with the interesting and uninteresting ld/st, I
will get the two trace entries for the 'i' and produce a WAR dependence
with distance != 0.
I just wonder how can I detect these kind of iteration (index)
variables, then I just need to do not insert recordload/store functions
into these "uninteresting" load/store instructions.
Thanks,
Henry
On Thu, Dec 11, 2014 at 6:43 PM, Das, Dibyendu <Dibyendu.Das at amd.com> wrote:
> I doubt there is any easy way to pick up ‘interesting ld/st’ and ignore
> the rest. If you are looking for...
2014 Dec 12
2
[LLVMdev] dynamic data dependence extraction using llvm
...not distinguish with the interesting and uninteresting ld/st, I
> will get the two trace entries for the 'i' and produce a WAR dependence
> with distance != 0.
>
> I just wonder how can I detect these kind of iteration (index)
> variables, then I just need to do not insert recordload/store functions
> into these "uninteresting" load/store instructions.
>
>
>
> Thanks,
>
> Henry
>
>
>
>
>
>
>
> On Thu, Dec 11, 2014 at 6:43 PM, Das, Dibyendu <Dibyendu.Das at amd.com>
> wrote:
>
> I doubt there is any easy way t...
2014 Dec 11
5
[LLVMdev] dynamic data dependence extraction using llvm
Hi LLVM-ers,
I try to develop my custom dynamic data dependence tool (focusing on nested
loops), currently I can successfully get the trace including load/store
address, loop information, etc.
However, when I try to analyze dynamic data dependence based on the
pairwise method described in [1], the load/store for iteration variables
may interfere my analysis (I only care about the load/store for