The VPM write logic will be basically the same as the texture coordinate write logic we need, and it's not really related to the VPM read logic other than the reuse of the use_count array.
27544ea vc4: Split optimizing VPM writes from VPM reads.
src/gallium/drivers/vc4/Makefile.sources | 1 +
.../drivers/vc4/vc4_opt_coalesce_ff_writes.c | 105 ++++++++++++++++++++
src/gallium/drivers/vc4/vc4_opt_vpm.c | 53 +---------
src/gallium/drivers/vc4/vc4_qir.c | 1 +
src/gallium/drivers/vc4/vc4_qir.h | 1 +
5 files changed, 110 insertions(+), 51 deletions(-)
Upstream: cgit.freedesktop.org