i965: handle OPCODE_SWZ in the glsl path
authorRoland Scheidegger <sroland@vmware.com>
Tue, 16 Jun 2009 19:38:58 +0000 (21:38 +0200)
committerIan Romanick <ian.d.romanick@intel.com>
Mon, 22 Jun 2009 22:15:20 +0000 (15:15 -0700)
glsl compiler will not generate OPCODE_SWZ, and as a first step it would
be translated away to a MOV anyway (why?), but later internally this opcode is
generated (for EXT_texture_swizzling).
(cherry picked from commit 4ef1f8e3b52a06fcf58f78c9c36738531b91dbac)

src/mesa/drivers/dri/i965/brw_wm_glsl.c

index 875683e0aa5f78c17d1f962ce9b731f6c65d2c04..094c1af2fef4f89882ebeaea2c85335b14609c51 100644 (file)
@@ -2681,6 +2681,7 @@ static void brw_wm_emit_glsl(struct brw_context *brw, struct brw_wm_compile *c)
                emit_trunc(c, inst);
                break;
            case OPCODE_MOV:
+           case OPCODE_SWZ:
                emit_mov(c, inst);
                break;
            case OPCODE_DP3: