From: Pyry Haulos <phaulos@google.com>
Date: Thu, 8 Jan 2015 21:16:54 +0000 (-0800)
Subject: Do not touch GL error state in postIterate()
X-Git-Tag: upstream/0.1.0~2016
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=e54007bd042c6063f6b78f66e489dd9827af056c;p=platform%2Fupstream%2FVK-GL-CTS.git

Do not touch GL error state in postIterate()

EGL implementation of RenderContext::postIterate() calls glFlush() when
rendering into a pixmap or pbuffer. This change removes erroneus
glGetError() call, as test case may want to carry error state over
iterate() calls.

Bug: 18915339
Change-Id: Ic8f4a1df46f74e8375e4f346daa3d2288f9ee39a
---

diff --git a/framework/egl/egluGLContextFactory.cpp b/framework/egl/egluGLContextFactory.cpp
index 980e27e..9f3a0af 100644
--- a/framework/egl/egluGLContextFactory.cpp
+++ b/framework/egl/egluGLContextFactory.cpp
@@ -605,11 +605,7 @@ void RenderContext::postIterate (void)
 		}
 	}
 	else
-	{
-		// \todo [2014-05-02 mika] Should we call flush or finish? Old platform uses finish() but flush() is closer to the behaviour of eglSwapBuffers()
 		m_glFunctions.flush();
-		GLU_EXPECT_NO_ERROR(m_glFunctions.getError(), "glFlush()");
-	}
 }
 
 } // anonymous