r600g: don't fail if we can't map VS->GS ring entries

This can happen in normal operation, so don't report an error on it,
just continue.

Signed-off-by: Dave Airlie <airlied@redhat.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>

diff --git a/src/gallium/drivers/r600/r600_shader.c b/src/gallium/drivers/r600/r600_shader.c
index 560672468749991ce838c57f6b8b54e0e4320403..73b290979fb40101a737810a570a90aeb4c2f7a4 100644 (file)
--- a/src/gallium/drivers/r600/r600_shader.c
+++ b/src/gallium/drivers/r600/r600_shader.c
@@ -1299,10 +1299,9 @@ static int emit_gs_ring_writes(struct r600_shader_ctx *ctx)
                                if (in->name == out->name && in->sid == out->sid)
                                        ring_offset = in->ring_offset;
                        }
-                       if (ring_offset == -1) {
-                               R600_ERR("error mapping VS->GS outputs\n");
-                               return -1;
-                       }
+
+                       if (ring_offset == -1)
+                               continue;
                } else
                        ring_offset = i * 16;