Mesa (master): i965/gs: Don't assign gl_Layer its own slot in the VUE map.

[Paul Berry]

Module: Mesa
Branch: master
Commit: 9dfa8ae662f522d7fb9e9be11a71a2eafc7985f0
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=9dfa8ae662f522d7fb9e9be11a71a2eafc7985f0

Author: Paul Berry <stereotype441 at gmail.com>
Date:   Tue Sep  3 13:57:35 2013 -0700

i965/gs: Don't assign gl_Layer its own slot in the VUE map.

Reviewed-by: Chad Versace <chad.versace at linux.intel.com>

---

 src/mesa/drivers/dri/i965/brw_vs.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/src/mesa/drivers/dri/i965/brw_vs.c b/src/mesa/drivers/dri/i965/brw_vs.c
index b81a538..7c7493f 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