mesa/st/program: don't init xfb info if there are no outputs
authorMike Blumenkrantz <michael.blumenkrantz@gmail.com>
Wed, 12 Apr 2023 16:57:13 +0000 (12:57 -0400)
committerMarge Bot <emma+marge@anholt.net>
Fri, 14 Apr 2023 01:12:08 +0000 (01:12 +0000)
commita86c710ce5869a55fb96498186f7dffc8e12c727
treed50c46420ec2e72c23296b5f5f22f1674da76411
parent9f4ec94c20e62dc2af05c0476ebd26368cf0abd4
mesa/st/program: don't init xfb info if there are no outputs

this is almost certainly a failure case, but drivers still shouldn't
get xfb info if there are no outputs

affects:
spec@glsl-1.50@execution@interface-blocks-api-access-members

cc: mesa-stable

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Marek Olšák <marek.olsak@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22448>
src/gallium/drivers/zink/ci/zink-anv-tgl-fails.txt
src/gallium/drivers/zink/ci/zink-radv-navi10-fails.txt
src/gallium/drivers/zink/ci/zink-radv-vangogh-fails.txt
src/mesa/state_tracker/st_program.c