[Mlir-commits] [mlir] 941f71a - [mlir] Fix ambiguity when building with Clang 14.0.6

[Alexandre Ganea]

Author: Alexandre Ganea
Date: 2022-10-05T12:16:54-04:00
New Revision: 941f71adf68e969b3832313fb9fe463c38377695

URL: https://github.com/llvm/llvm-project/commit/941f71adf68e969b3832313fb9fe463c38377695
DIFF: https://github.com/llvm/llvm-project/commit/941f71adf68e969b3832313fb9fe463c38377695.diff

LOG: [mlir] Fix ambiguity when building with Clang 14.0.6

Differential revision: https://reviews.llvm.org/D134219

Added: 
    

Modified: 
    mlir/unittests/Analysis/Presburger/IntegerPolyhedronTest.cpp

Removed: 
    


################################################################################
diff  --git a/mlir/unittests/Analysis/Presburger/IntegerPolyhedronTest.cpp b/mlir/unittests/Analysis/Presburger/IntegerPolyhedronTest.cpp
index 1be5a3f04bf59..b38f137c7c245 100644
--- a/mlir/unittests/Analysis/Presburger/IntegerPolyhedronTest.cpp
+++ b/mlir/unittests/Analysis/Presburger/IntegerPolyhedronTest.cpp
@@ -1479,9 +1479,7 @@ TEST(IntegerPolyhedronTest, containsPointNoLocal) {
   IntegerPolyhedron poly3 =
       parseIntegerPolyhedron("(x, y) : (2*x - y >= 0, y - 3*x >= 0)");
 
-  // -0 instead of 0 to prevent unwanted conversion to pointer types,
-  // which would lead to ambiguity in overload resolution.
-  EXPECT_TRUE(poly3.containsPointNoLocal({-0, 0}));
+  EXPECT_TRUE(poly3.containsPointNoLocal(ArrayRef<int64_t>({0, 0})));
   EXPECT_FALSE(poly3.containsPointNoLocal({1, 0}));
 }