[llvm] [LAA] Use MaxStride instead of CommonStride to calculate MaxVF (PR #98142)

[LLVM Continuous Integration via llvm-commits]

llvm-ci wrote:

LLVM Buildbot has detected a new failure on builder `lld-x86_64-ubuntu-fast` running on `as-builder-4` while building `llvm` at step 6 "test-build-unified-tree-check-all".

Full details are available at: https://lab.llvm.org/buildbot/#/builders/33/builds/16064

<details>
<summary>Here is the relevant piece of the build log for the reference</summary>

```
Step 6 (test-build-unified-tree-check-all) failure: test (failure)
******************** TEST 'LLVM :: Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll' FAILED ********************
Exit Code: 1

Command Output (stderr):
--
/home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/opt -passes='print<access-info>' -disable-output /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll 2>&1 | /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/FileCheck /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll # RUN: at line 2
+ /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/opt '-passes=print<access-info>' -disable-output /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll
+ /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/build/bin/FileCheck /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll
/home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll:112:15: error: CHECK-NEXT: expected string not found in input
; CHECK-NEXT: Report: unsafe dependent memory operations in loop. Use #pragma clang loop distribute(enable) to allow loop distribution to attempt to isolate the offending operations into a separate loop
              ^
<stdin>:39:7: note: scanning from here
 loop:
      ^

Input file: <stdin>
Check file: /home/buildbot/worker/as-builder-4/ramdisk/lld-x86_64/llvm-project/llvm/test/Analysis/LoopAccessAnalysis/different-strides-safe-dep-due-to-backedge-taken-count.ll

-dump-input=help explains the following input dump.

Input was:
<<<<<<
          .
          .
          .
         34:  Non vectorizable stores to invariant address were not found in loop. 
         35:  SCEV assumptions: 
         36:  
         37:  Expressions re-written: 
         38: Printing analysis 'Loop Access Analysis' for function 'unknown_dep_not_known_safe_due_to_backedge_taken_count': 
         39:  loop: 
next:112           X error: no match found
         40:  Memory dependences are safe with a maximum safe vector width of 8160 bits 
next:112     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         41:  Dependences: 
next:112     ~~~~~~~~~~~~~~
         42:  BackwardVectorizable: 
next:112     ~~~~~~~~~~~~~~~~~~~~~~~
         43:  %l = load i32, ptr %gep, align 4 ->  
next:112     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         44:  store i32 %add, ptr %gep.mul.2, align 4 
next:112     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          .
          .
          .
>>>>>>

--

********************


```

</details>

https://github.com/llvm/llvm-project/pull/98142