Framebuffer: Fix getDepthStencilAttachment check.

The check should be using the newer operator== to check if attachments are the same - the id() method will hit an UNREACHABLE if it's called on a Surface attachment. I noticed this when using this method in the Vulkan RenderPass implementation. BUG=angleproject:1583 Change-Id: I387b35805893d04003b22a1c7c9c12fc41c726ce Reviewed-on: https://chromium-review.googlesource.com/412801Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org>

Framebuffer: Fix getDepthStencilAttachment check.
44f26482 · Jamie Madill · Commit Bot · 861ebb3b · 44f26482
Commit 44f26482 authored Nov 18, 2016 by Jamie Madill Committed by Commit Bot Nov 18, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 2 deletions

Framebuffer.cpp src/libANGLE/Framebuffer.cpp +1 -2

No files found.
--- a/src/libANGLE/Framebuffer.cpp
+++ b/src/libANGLE/Framebuffer.cpp
@@ -151,8 +151,7 @@ const FramebufferAttachment *FramebufferState::getDepthStencilAttachment() const
    // A valid depth-stencil attachment has the same resource bound to both the
    // depth and stencil attachment points.
    if (mDepthAttachment.isAttached() && mStencilAttachment.isAttached() &&
-        mDepthAttachment.type() == mStencilAttachment.type() &&
-        mDepthAttachment.id() == mStencilAttachment.id())
+        mDepthAttachment == mStencilAttachment)
    {
        return &mDepthAttachment;
    }