diff options
| author | Kenneth Graunke <[email protected]> | 2016-05-10 17:54:45 -0700 |
|---|---|---|
| committer | Kenneth Graunke <[email protected]> | 2016-06-16 14:37:07 -0700 |
| commit | 1f9445ff57b03413c433731bc00572029da10aa9 (patch) | |
| tree | 1884a00b597fc5989341e620c370d4425113d4b1 /src | |
| parent | 32b1c0b694bf660d48054a6e859deaa8f9556efe (diff) | |
i965: Drop perf_debug about rasterizer discard in SOL vs. clipper.
I recently experimented with performing rasterizer discard in the SOL
unit instead of the clipper, and as far as I can tell, it's basically
the same performance. The clipper comes directly after SOL anyway,
and setting the clipper to REJECT_ALL should be pretty darn cheap.
Keep the perf_debug on Sandybridge, where the GS actually does work.
Signed-off-by: Kenneth Graunke <[email protected]>
Diffstat (limited to 'src')
| -rw-r--r-- | src/mesa/drivers/dri/i965/gen6_clip_state.c | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/src/mesa/drivers/dri/i965/gen6_clip_state.c b/src/mesa/drivers/dri/i965/gen6_clip_state.c index 26de633bae6..b079ffdd6da 100644 --- a/src/mesa/drivers/dri/i965/gen6_clip_state.c +++ b/src/mesa/drivers/dri/i965/gen6_clip_state.c @@ -165,9 +165,11 @@ upload_clip_state(struct brw_context *brw) /* BRW_NEW_RASTERIZER_DISCARD */ if (ctx->RasterDiscard) { dw2 |= GEN6_CLIP_MODE_REJECT_ALL; - perf_debug("Rasterizer discard is currently implemented via the clipper; " - "%s be faster.\n", brw->gen >= 7 ? "using the SOL unit may" : - "having the GS not write primitives would likely"); + if (brw->gen == 6) { + perf_debug("Rasterizer discard is currently implemented via the " + "clipper; having the GS not write primitives would " + "likely be faster.\n"); + } } uint32_t enable; |