diff options
| author | Kristian Høgsberg <[email protected]> | 2014-05-12 15:46:11 -0700 |
|---|---|---|
| committer | Kristian Høgsberg <[email protected]> | 2014-06-18 10:15:03 -0700 |
| commit | 7928b946adbcbbb835c0080967bbb538f6bd35dc (patch) | |
| tree | e18e0e8275f135f58f1bd31ae4d4635df46862b3 /src | |
| parent | fe5224b16a7a614fad07edee86cdcc8f47446f5e (diff) | |
mesa: Remove glClear optimization based on drawable size
A drawable size of 0x0 means that we don't have buffers for a drawable yet,
not that we have a zero-sized buffer. Core mesa shouldn't be optimizing out
drawing based on buffer size, since the draw call could be what triggers
the driver to go and get buffers. As discussed in the referenced bug report,
the optimization was added as part of a scatter-shot attempt to fix a
different problem. There's no other example in mesa core of using the
buffer size in this way.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74005
Cc: "10.1 10.2" <[email protected]>
Signed-off-by: Kristian Høgsberg <[email protected]>
Reviewed-by: Ian Romanick <[email protected]>
Diffstat (limited to 'src')
| -rw-r--r-- | src/mesa/main/clear.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/src/mesa/main/clear.c b/src/mesa/main/clear.c index 9df1f5e098c..cf93418d10f 100644 --- a/src/mesa/main/clear.c +++ b/src/mesa/main/clear.c @@ -180,11 +180,6 @@ _mesa_Clear( GLbitfield mask ) return; } - if (ctx->DrawBuffer->Width == 0 || ctx->DrawBuffer->Height == 0 || - ctx->DrawBuffer->_Xmin >= ctx->DrawBuffer->_Xmax || - ctx->DrawBuffer->_Ymin >= ctx->DrawBuffer->_Ymax) - return; - if (ctx->RasterDiscard) return; |