From 836102fbe306bc6d93b8dc54a690af2669cd28ad Mon Sep 17 00:00:00 2001
From: Reed Wanderman-Milne <reedwm@google.com>
Date: Wed, 22 Apr 2020 14:02:12 -0700
Subject: [PATCH] Change incorrect padding comment.
The padded area is not zero-filled for pooling ops, despite the comment.
PiperOrigin-RevId: 307893632
Change-Id: I570773b6bbbd6f79f738e3930828456a3d77252d
---
tensorflow/core/util/padding.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tensorflow/core/util/padding.h b/tensorflow/core/util/padding.h
index 6c109d15d36..90e353d23fa 100644
--- a/tensorflow/core/util/padding.h
+++ b/tensorflow/core/util/padding.h
@@ -38,7 +38,8 @@ class NodeDef;
// dimensions as the input.
// EXPLICIT: The user specifies the pad values in the explicit_paddings
// attribute.
-// The padded area is zero-filled.
+// The padded area is typically zero-filled. For pooling ops, the padded area is
+// instead ignored. For max pool, this is equivalent to padding with -infinity.
enum Padding {
VALID = 1, // No padding.
SAME = 2, // Input and output layers have the same size.