[LoopAccessAnalysis] Add a const qualifier to getMaxSafeDepDistBytes()

[vedant-amd]

Summary

Add a const qualifier to this API call, since this is a member of
MemoryDepChecker and LoopAccessInfo returns an object of this class as a
const, as follows:

const MemoryDepChecker &getDepChecker() const { return *DepChecker; }

If one tries to use function as follows:

LAI->getDepChecker().getMaxSafeDepDistBytes()

results in the following error:

passing ‘const llvm::MemoryDepChecker’ as ‘this’ argument discards
qualifiers

[vedant-amd]

ping !

[vedant-amd]

ping @fhahn , @sdesmalen can you please review this once ? Thanks !

[nikic]

LGTM, please add NFC to the patch title.

[vedant-amd]

In D156304#4545880, @nikic wrote:

LGTM, please add NFC to the patch title.

Sorry, I forgot to add NFC. Is it possible to rebase and submit again ? or it's fine as it is ?

llvm/include/llvm/Analysis/LoopAccessAnalysis.h

public:
   /// Return true if the number of elements that are safe to operate on
   /// simultaneously is not bounded.
   bool isSafeForAnyVectorWidth() const {
     return MaxSafeVectorWidthInBits == UINT_MAX;
   }
 
   /// The maximum number of bytes of a vector register we can vectorize
   /// the accesses safely with.
-  uint64_t getMaxSafeDepDistBytes() { return MaxSafeDepDistBytes; }
+  uint64_t getMaxSafeDepDistBytes() const { return MaxSafeDepDistBytes; }
 
   /// Return the number of elements that are safe to operate on
   /// simultaneously, multiplied by the size of the element in bits.
   uint64_t getMaxSafeVectorWidthInBits() const {
     return MaxSafeVectorWidthInBits;
   }
 
   /// In same cases when the dependency check fails we can still