nv40: workaround fp result.data[0] clobberage

Temporary, the fp reg handling will get reworked at some point in the near
future.  But before that, there's a few bugs to find.

diff --git a/src/gallium/drivers/nv40/nv40_fragprog.c b/src/gallium/drivers/nv40/nv40_fragprog.c
index 2d82f86ef5c2721a42531ec080228ed4938d8a03..4e425366985f4d446d31bd62a17ffb45f22e6bd9 100644 (file)
--- a/src/gallium/drivers/nv40/nv40_fragprog.c
+++ b/src/gallium/drivers/nv40/nv40_fragprog.c
@@ -58,7 +58,7 @@ temp(struct nv40_fpc *fpc)
        int idx;
 
        idx  = fpc->temp_temp_count++;
-       idx += fpc->high_temp + 1;
+       idx += fpc->high_temp + 2;
        return nv40_sr(NV40SR_TEMP, idx);
 }
 
@@ -817,7 +817,9 @@ nv40_fragprog_upload(struct nv40_context *nv40,
 
 #if 0
        for (i = 0; i < fp->insn_len; i++) {
+               fflush(stdout); fflush(stderr);
                NOUVEAU_ERR("%d 0x%08x\n", i, fp->insn[i]);
+               fflush(stdout); fflush(stderr);
        }
 #endif