Displaying 3 results from an estimated 3 matches for "chainlatency".
2014 Dec 14
2
[LLVMdev] ScheduleDAGInstrs.cpp
...e thus not in RejectMemNodes) that have a dependency on the new AliasChain.
Or am I missing something? Very interested in your opinion.
I am thinking of something like
new_alias_chain:
// Chain all possibly aliasing memory references through SU.
if (AliasChain) {
unsigned ChainLatency = 0;
if (AliasChain->getInstr()->mayLoad()) ChainLatency = TrueMemOrderLatency;
addChainDependency(AAForDep, MFI, SU, AliasChain, RejectMemNodes,
ChainLatency);
+
+ // Since TII->areMemAccessesTriviallyDisjoint() is not
+...
2014 Dec 08
3
[LLVMdev] ScheduleDAGInstrs.cpp
Hi,
Can anyone help me to understand the ScheduleDAGInstrs::buildSchedGraph() method?
I find the handling of AliasChain is disturbing since:
1. A new alias chain add deps to all possibly aliasing SUs, and then clears those lists.
2. When AliasChain is present, the addChainDependency() method is called,
but the target hook areMemAccessesTriviallyDisjoint() called inside
2014 Dec 16
3
[LLVMdev] ScheduleDAGInstrs.cpp
...dependency on the new AliasChain.
>
> Or am I missing something? Very interested in your opinion.
>
> I am thinking of something like
>
> new_alias_chain:
> // Chain all possibly aliasing memory references through SU.
> if (AliasChain) {
> unsigned ChainLatency = 0;
> if (AliasChain->getInstr()->mayLoad()) ChainLatency = TrueMemOrderLatency;
> addChainDependency(AAForDep, MFI, SU, AliasChain, RejectMemNodes,
> ChainLatency);
> +
> + // Since TII->areMemAccessesTriviallyDisj...