Mesa (master): i965/curbe: Look at SYSTEM_VALUE_FRAG_COORD instead of VARYING_SLOT_POS

[GitLab Mirror]

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

Author: Jason Ekstrand <jason at jlekstrand.net>
Date:   Tue Jul 30 18:07:08 2019 -0500

i965/curbe: Look at SYSTEM_VALUE_FRAG_COORD instead of VARYING_SLOT_POS

When transitioning gl_FragCoord over to a system value, we missed one
instance of VARYING_SLOT_POS in i965.  As of this commit, i965 has no
references to VARYING_SLOT_POS.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111263
Fixes: 4bb6e6817ec "intel: Use a system value for gl_FragCoord"
Reviewed-by: Kenneth Graunke <kenneth at whitecape.org>

---

 src/mesa/drivers/dri/i965/brw_curbe.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/mesa/drivers/dri/i965/brw_curbe.c b/src/mesa/drivers/dri/i965/brw_curbe.c
index eb824739c67..abe8d099a19 100644
--- a/src/mesa/drivers/dri/i965/brw_curbe.c
+++ b/src/mesa/drivers/dri/i965/brw_curbe.c
@@ -332,7 +332,7 @@ emit:
     * BRW_NEW_FRAGMENT_PROGRAM
     */
    if (devinfo->gen == 4 && !devinfo->is_g4x &&
-       (fp->info.inputs_read & (1 << VARYING_SLOT_POS))) {
+       (fp->info.system_values_read & (1ull << SYSTEM_VALUE_FRAG_COORD))) {
       BEGIN_BATCH(2);
       OUT_BATCH(_3DSTATE_GLOBAL_DEPTH_OFFSET_CLAMP << 16 | (2 - 2));
       OUT_BATCH(0);