[ValueTracking] Change recursive eval order for isKnownNonZero(umin); NFC

[goldsteinn]

Doing arg1 is generally preferable as its more likely to be a constant
which will evaluate quickly.

[llvmbot]

@llvm/pr-subscribers-llvm-analysis

Author: None (goldsteinn)

Changes

Doing arg1 is generally preferable as its more likely to be a constant
which will evaluate quickly.

---

Full diff: https://github.com/llvm/llvm-project/pull/83607.diff

1 Files Affected:

• (modified) llvm/lib/Analysis/ValueTracking.cpp (+2-2)

diff --git a/llvm/lib/Analysis/ValueTracking.cpp b/llvm/lib/Analysis/ValueTracking.cpp
index e591ac504e9f05..12dc39f3743fcc 100644
--- a/llvm/lib/Analysis/ValueTracking.cpp
+++ b/llvm/lib/Analysis/ValueTracking.cpp
@@ -2742,8 +2742,8 @@ static bool isKnownNonZeroFromOperator(const Operator *I,
       }
         [[fallthrough]];
       case Intrinsic::umin:
-        return isKnownNonZero(II->getArgOperand(0), DemandedElts, Depth, Q) &&
-               isKnownNonZero(II->getArgOperand(1), DemandedElts, Depth, Q);
+        return isKnownNonZero(II->getArgOperand(1), DemandedElts, Depth, Q) &&
+               isKnownNonZero(II->getArgOperand(0), DemandedElts, Depth, Q);
       case Intrinsic::cttz:
         return computeKnownBits(II->getArgOperand(0), DemandedElts, Depth, Q)
             .Zero[0];

[goldsteinn]

Realized umin(0) will just simplify to zero...