From: Paul Berry Date: Tue, 3 Sep 2013 20:57:35 +0000 (-0700) Subject: i965/gs: Don't assign gl_Layer its own slot in the VUE map. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=9dfa8ae662f522d7fb9e9be11a71a2eafc7985f0;p=mesa.git i965/gs: Don't assign gl_Layer its own slot in the VUE map. Reviewed-by: Chad Versace --- diff --git a/src/mesa/drivers/dri/i965/brw_vs.c b/src/mesa/drivers/dri/i965/brw_vs.c index b81a53856a0..7c7493f9632 100644 --- a/src/mesa/drivers/dri/i965/brw_vs.c +++ b/src/mesa/drivers/dri/i965/brw_vs.c @@ -64,6 +64,11 @@ brw_compute_vue_map(struct brw_context *brw, struct brw_vue_map *vue_map, vue_map->slots_valid = slots_valid; int i; + /* gl_Layer doesn't get its own varying slot--it's stored in the virst VUE + * slot (VARYING_SLOT_PSIZ). + */ + slots_valid &= ~VARYING_BIT_LAYER; + /* Make sure that the values we store in vue_map->varying_to_slot and * vue_map->slot_to_varying won't overflow the signed chars that are used * to store them. Note that since vue_map->slot_to_varying sometimes holds