mesa: don't flush and don't flag _NEW_STENCIL in ClearStencil, ActiveStencilFace
The functions don't affect driver state. There is no code that would rely on vertices being flushed prior to changing the states, and no code that would check for _NEW_STENCIL before using the states. Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Eric Anholt <eric@anholt.net>
This commit is contained in:
@@ -109,10 +109,6 @@ _mesa_ClearStencil( GLint s )
|
||||
{
|
||||
GET_CURRENT_CONTEXT(ctx);
|
||||
|
||||
if (ctx->Stencil.Clear == (GLuint) s)
|
||||
return;
|
||||
|
||||
FLUSH_VERTICES(ctx, _NEW_STENCIL);
|
||||
ctx->Stencil.Clear = (GLuint) s;
|
||||
}
|
||||
|
||||
@@ -390,7 +386,6 @@ _mesa_ActiveStencilFaceEXT(GLenum face)
|
||||
}
|
||||
|
||||
if (face == GL_FRONT || face == GL_BACK) {
|
||||
FLUSH_VERTICES(ctx, _NEW_STENCIL);
|
||||
ctx->Stencil.ActiveFace = (face == GL_FRONT) ? 0 : 2;
|
||||
}
|
||||
else {
|
||||
|
||||
Reference in New Issue
Block a user