Lines Matching defs:LVI

97 ///   not confuse the rest of LVI.  Ideally, we'd always return Undefined, but
528     // PredicateInfo is used in LVI or CVP, we should be able to make the
1531   LLVM_DEBUG(dbgs() << "LVI Getting block end value " << *V << " at '"
1548   LLVM_DEBUG(dbgs() << "LVI Getting value " << *V << " at '" << CxtI->getName()
1566   LLVM_DEBUG(dbgs() << "LVI Getting edge value " << *V << " from '"
1867   // Note: The following bit of code is somewhat distinct from the rest of LVI;
1868   // LVI as a whole tries to compute a lattice value which is conservatively
2001 // Print the LVI for the function arguments at the start of each basic block.
2015 // This function prints the LVI analysis for the instruction I at the beginning
2024   // We can generate (solve) LVI values only for blocks that are dominated by
2025   // the I's parent. However, to avoid generating LVI for all dominating blocks,
2026   // that contain redundant/uninteresting information, we print LVI for
2027   // blocks that may use this LVI information (such as immediate successor
2040   // Print the LVI analysis results for the immediate successor blocks, that
2046   // Print LVI in blocks where `I` is used.
2056   OS << "LVI for function '" << F.getName() << "':\n";
2057   auto &LVI = AM.getResult<LazyValueAnalysis>(F);
2059   LVI.printLVI(F, DTree, OS);