Attachment 63472 Details for Bug 50149 – Possible fix patch 2

[patch] Possible fix patch 2

0002-r300-compiler-Increase-default-value-of-max_tex_grou.patch (text/plain), 1.33 KB, created by Tom Stellard on 2012-06-25 19:13:09 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Tom Stellard

Created: 2012-06-25 19:13:09 UTC

Size: 1.33 KB

patch

obsolete

>From e31c52124a4518dad3dd9c8a1fee0d08ea5dd005 Mon Sep 17 00:00:00 2001
>From: Tom Stellard <thomas.stellard@amd.com>
>Date: Mon, 25 Jun 2012 22:08:01 -0400
>Subject: [PATCH 2/2] r300/compiler: Increase default value of max_tex_group on < r500
>
>---
> .../drivers/r300/compiler/radeon_pair_schedule.c   |    3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
>diff --git a/src/gallium/drivers/r300/compiler/radeon_pair_schedule.c b/src/gallium/drivers/r300/compiler/radeon_pair_schedule.c
>index df54b08..45e4dc9 100644
>--- a/src/gallium/drivers/r300/compiler/radeon_pair_schedule.c
>+++ b/src/gallium/drivers/r300/compiler/radeon_pair_schedule.c
>@@ -1325,6 +1325,7 @@ void rc_pair_schedule(struct radeon_compiler *cc, void *user)
> 	struct schedule_state s;
> 	struct rc_instruction * inst = c->Base.Program.Instructions.Next;
> 	unsigned int * opt = user;
>+	unsigned default_max_tex_group = cc->is_r500 ? 8 : (cc->is_r400 ? 128 : 32);
> 
> 	memset(&s, 0, sizeof(s));
> 	s.Opt = *opt;
>@@ -1334,7 +1335,7 @@ void rc_pair_schedule(struct radeon_compiler *cc, void *user)
> 	} else {
> 		s.CalcScore = calc_score_r300;
> 	}
>-	s.max_tex_group = debug_get_num_option("RADEON_TEX_GROUP", 8);
>+	s.max_tex_group = debug_get_num_option("RADEON_TEX_GROUP", default_max_tex_group);
> 	while(inst != &c->Base.Program.Instructions) {
> 		struct rc_instruction * first;
> 
>-- 
>1.7.3.4
>

Actions: View | Splinter Review

Attachments on bug 50149: 61930 | 61931 | 61932 | 62124 | 62125 | 62189 | 63471 | 63472 | 67361 | 67362 | 67899 | 67926

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.