[llvm] [LAA] Add initial support for non-power-of-2 store-load forwarding distance (PR #137873)

[Florian Hahn via llvm-commits]

================
@@ -1731,24 +1732,61 @@ bool MemoryDepChecker::couldPreventStoreLoadForward(uint64_t Distance,
       break;
     }
   }
+  // RISCV VLA supports non-power-2 vector factor. So, we iterate in a
+  // backward order to find largest VF, which allows aligned stores-loads or
+  // the number of iterations between conflicting memory addresses is not less
+  // than 8 (NumItersForStoreLoadThroughMemory).
+  if (AllowNonPow2Deps) {
+    MaxVFWithoutSLForwardIssuesNonPowerOf2 =
+        std::min(8 * VectorizerParams::MaxVectorWidth / TypeByteSize,
+                 MaxNonPowerOf2StoreLoadForwardSafeDistanceInBits);
+
+    for (uint64_t VF = MaxVFWithoutSLForwardIssuesNonPowerOf2;
----------------
fhahn wrote:

Ok I see. But then it behaves different to `MaxVFWithoutSLForwardIssuesPowerOf2`. With `MaxVFWithoutSLForwardIssuesPowerOf2` limits the Max VF we can use and we can also use any VF between 1 and MaxVF.

Is `MaxVFWithoutSLForwardIssuesNonPowerOf2` a single non-power-of-2 VF we can use, but other VFs between 1 .. MaxVFWithoutSLForwardIssuesNonPowerOf2 may not be used?

Am I understanding correctly for example with, Max pow2 VF = 2, MaxNonPowOf2 VF = 9, LV can either chose 2 or 16 (with limiting VF to 9)?

If that's the case, I think it. would be good to update the comment for `MaxNonPowerOf2StoreLoadForwardSafeDistanceInBits` to make this difference to the power-of-2 variant clear, as they would behave quite differently.


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