Vulkan: properly handle 0-width or 0-height framebuffers

The test for whether 0-width or 0-height is not given was doing width != 0 || height != 0 which mistakenly used || instead of &&. Bug: angleproject:2910 Change-Id: Iaa41edffcfe1f8553e8fbefb9bc3b12a7f33a5a6 Reviewed-on: https://chromium-review.googlesource.com/c/1316028Reviewed-by: Geoff Lang <geofflang@chromium.org> Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>

Vulkan: properly handle 0-width or 0-height framebuffers
3d86e89b · Shahbaz Youssefi · Commit Bot · 37297a4f · 3d86e89b
Commit 3d86e89b authored Nov 02, 2018 by Shahbaz Youssefi Committed by Commit Bot Nov 05, 2018
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

RenderbufferVk.cpp src/libANGLE/renderer/vulkan/RenderbufferVk.cpp +1 -1

No files found.
--- a/src/libANGLE/renderer/vulkan/RenderbufferVk.cpp
+++ b/src/libANGLE/renderer/vulkan/RenderbufferVk.cpp
@@ -62,7 +62,7 @@ angle::Result RenderbufferVk::setStorage(const gl::Context *context,
        }
    }

-    if (!mImage.valid() && (width != 0 || height != 0))
+    if (!mImage.valid() && (width != 0 && height != 0))
    {
        const angle::Format &textureFormat = vkFormat.textureFormat();
        bool isDepthOrStencilFormat = textureFormat.depthBits > 0 || textureFormat.stencilBits > 0;