intel/fs: use pull constant locations to check for first compile of a shader
authorJason Ekstrand <jason.ekstrand@intel.com>
Tue, 22 Aug 2017 01:42:41 +0000 (18:42 -0700)
committerJason Ekstrand <jason.ekstrand@intel.com>
Tue, 7 Nov 2017 18:37:52 +0000 (10:37 -0800)
commitb299ded02eccfa94aede65086bd1ad254aaa5180
treedac5963f2b20449b08cbca5d0c521fd938bac9f4
parent103081c9a9912a11b47077b8e25efdbbb3d65e10
intel/fs: use pull constant locations to check for first compile of a shader

Before, we bailing in assign_constant_locations based on the minimum
dispatch size.  The more direct thing to do is simply to check for
whether or not we have constant locations and bail if we do.  For
nir_setup_uniforms, it's completely safe to do it multiple times because
we just copy a value from the NIR shader.

Reviewed-by: Iago Toral Quiroga <itoral@igalia.com>
src/intel/compiler/brw_fs.cpp
src/intel/compiler/brw_fs_nir.cpp