From 7d98596bfaac7c5055a1ee8533f2361b09032f5b Mon Sep 17 00:00:00 2001 From: Dwayne Robinson Date: Tue, 10 Nov 2020 21:05:59 +0000 Subject: [PATCH] Merged PR 5390213: Tile allow 0 in repeats 0 is valid in Tile in "repeats" parameter. The CPU kernel handles it fine. So should the DML EP. Related work items: #29970551 --- .../core/providers/dml/OperatorAuthorHelper/OperatorHelper.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/onnxruntime/core/providers/dml/OperatorAuthorHelper/OperatorHelper.h b/onnxruntime/core/providers/dml/OperatorAuthorHelper/OperatorHelper.h index 3bd8064dc6..06250fddce 100644 --- a/onnxruntime/core/providers/dml/OperatorAuthorHelper/OperatorHelper.h +++ b/onnxruntime/core/providers/dml/OperatorAuthorHelper/OperatorHelper.h @@ -1273,7 +1273,7 @@ class TileHelper { ML_CHECK_VALID_ARGUMENT(repeatsTensor.IsCpuData(), "Tile's repeats tensor must be CPU Tensor."); for (size_t i = 0; i < dimCount; ++i) { - ML_CHECK_VALID_ARGUMENT(repeatsData[i] > 0, "Repeat values should be > 0."); + ML_CHECK_VALID_ARGUMENT(repeatsData[i] >= 0, "Repeat values should be >= 0."); m_repeatsData.push_back(gsl::narrow_cast(repeatsData[i])); }