st/mesa: don't use _NEW_PROGRAM where ST_NEW_xxx_PROGRAM is sufficient

Reviewed-by: Brian Paul <brianp@vmware.com>
This commit is contained in:
Marek Olšák
2012-10-29 03:09:50 +01:00
parent c0c26ddaef
commit 0ebd0b78c6
3 changed files with 6 additions and 6 deletions

View File

@@ -588,7 +588,7 @@ static void update_array(struct st_context *st)
const struct st_tracked_state st_update_array = {
"st_update_array", /* name */
{ /* dirty */
(_NEW_PROGRAM | _NEW_BUFFER_OBJECT), /* mesa */
_NEW_BUFFER_OBJECT, /* mesa */
ST_NEW_VERTEX_ARRAYS | ST_NEW_VERTEX_PROGRAM, /* st */
},
update_array /* update */

View File

@@ -67,8 +67,8 @@ static void update_clip( struct st_context *st )
const struct st_tracked_state st_update_clip = {
"st_update_clip", /* name */
{ /* dirty */
(_NEW_TRANSFORM | _NEW_PROGRAM), /* mesa */
0, /* st */
_NEW_TRANSFORM, /* mesa */
ST_NEW_VERTEX_PROGRAM, /* st */
},
update_clip /* update */
};

View File

@@ -125,7 +125,7 @@ static void update_vs_constants(struct st_context *st )
const struct st_tracked_state st_update_vs_constants = {
"st_update_vs_constants", /* name */
{ /* dirty */
(_NEW_PROGRAM | _NEW_PROGRAM_CONSTANTS), /* mesa */
_NEW_PROGRAM_CONSTANTS, /* mesa */
ST_NEW_VERTEX_PROGRAM, /* st */
},
update_vs_constants /* update */
@@ -148,7 +148,7 @@ static void update_fs_constants(struct st_context *st )
const struct st_tracked_state st_update_fs_constants = {
"st_update_fs_constants", /* name */
{ /* dirty */
(_NEW_PROGRAM | _NEW_PROGRAM_CONSTANTS), /* mesa */
_NEW_PROGRAM_CONSTANTS, /* mesa */
ST_NEW_FRAGMENT_PROGRAM, /* st */
},
update_fs_constants /* update */
@@ -170,7 +170,7 @@ static void update_gs_constants(struct st_context *st )
const struct st_tracked_state st_update_gs_constants = {
"st_update_gs_constants", /* name */
{ /* dirty */
(_NEW_PROGRAM | _NEW_PROGRAM_CONSTANTS), /* mesa */
_NEW_PROGRAM_CONSTANTS, /* mesa */
ST_NEW_GEOMETRY_PROGRAM, /* st */
},
update_gs_constants /* update */