[llvm] [KnownBits] Remove `hasConflict()` assertions (PR #94568)

Nikita Popov via llvm-commits llvm-commits at lists.llvm.org
Fri Jun 7 05:41:57 PDT 2024


================
@@ -403,8 +391,7 @@ KnownBits KnownBits::lshr(const KnownBits &LHS, const KnownBits &RHS,
   if (Exact) {
     unsigned FirstOne = LHS.countMaxTrailingZeros();
     if (FirstOne < MinShiftAmount) {
-      // Always poison. Return zero because we don't like returning conflict.
-      Known.setAllZero();
+      // Always poison.
----------------
nikic wrote:

Hm, I see. In that case I think it would be best to just revert *all* the setAllZero() related changes. We will have to update consuming code first so it can do something useful with conflict values before we start generating them.

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


More information about the llvm-commits mailing list