From 1f9445ff57b03413c433731bc00572029da10aa9 Mon Sep 17 00:00:00 2001 From: Kenneth Graunke Date: Tue, 10 May 2016 17:54:45 -0700 Subject: 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 --- src/mesa/drivers/dri/i965/gen6_clip_state.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'src/mesa/drivers/dri/i965') 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; -- cgit v1.2.3