[AMDGPU] Do not consider indirect acces through phi for wave limiter

Rational: if there is indirect access that is usually an issue
because load is not ready by the use. However, if use is inside a
loop and load is outside that is potentially an issue for a first
iteration only.

Differential Revision: https://reviews.llvm.org/D47740

llvm-svn: 334420

1 files changed, 0 insertions, 6 deletions

diff --git a/llvm/lib/Target/AMDGPU/AMDGPUPerfHintAnalysis.cpp b/llvm/lib/Target/AMDGPU/AMDGPUPerfHintAnalysis.cpp
index d307f818d7b..3cfdccc9fe5 100644
--- a/llvm/lib/Target/AMDGPU/AMDGPUPerfHintAnalysis.cpp
+++ b/llvm/lib/Target/AMDGPU/AMDGPUPerfHintAnalysis.cpp
@@ -198,12 +198,6 @@ bool AMDGPUPerfHint::isIndirectAccess(const Instruction *Inst) const {
       continue;
     }
 
-    if (auto Phi = dyn_cast<PHINode>(V)) {
-      for (unsigned I = 0, E = Phi->getNumIncomingValues(); I != E; ++I)
-        WorkSet.insert(Phi->getIncomingValue(I));
-      continue;
-    }
-
     LLVM_DEBUG(dbgs() << "    dropped\n");
   }