glsl: Don't do copy propagation on buffer variables
authorIago Toral Quiroga <itoral@igalia.com>
Fri, 24 Apr 2015 09:17:15 +0000 (11:17 +0200)
committerSamuel Iglesias Gonsalvez <siglesias@igalia.com>
Tue, 14 Jul 2015 05:04:04 +0000 (07:04 +0200)
commit2a66ee6fc1fa1e64f2d9a22271187d4462d9e042
tree4560753b52bebe87633553f60cf5ef2396cdfa40
parent5dfea83ee6bf85fb3962679d043eb06b33bfd4c1
glsl: Don't do copy propagation on buffer variables

Since the backing storage for these is shared we cannot ensure that
the value won't change by writes from other threads. Normally SSBO
accesses are not guaranteed to be syncronized with other threads,
except when memoryBarrier is used. So, we might be able to optimize
some SSBO accesses, but for now we always take the safe path and emit
the SSBO access.

Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
src/glsl/opt_copy_propagation.cpp