summaryrefslogtreecommitdiffstats
path: root/progs/vp
diff options
context:
space:
mode:
authorKenneth Graunke <[email protected]>2015-04-09 23:26:49 -0700
committerJason Ekstrand <[email protected]>2015-04-10 16:22:48 -0700
commitc2a0600d5b0645533ba442b5ab879b23c2564a4d (patch)
tree1a3cb3ffa016a1e453b5b5c7b6f93ad4050f1e96 /progs/vp
parentf9048ee3c85ddaff0c44851b2523aaa2a554e059 (diff)
i965: Don't set NirOptions for stages that will use the vec4 backend.cros-mesa-10.6-vanillachadv/cros-mesa-10.6-vanillachadv/cros-gerrit-262788-base
We've started using NirOptions != NULL to mean "we're using NIR for this stage." However, when INTEL_USE_NIR=1, we set it for a bunch of stages that still use the vec4 backend, and thus definitely aren't using NIR. For example, if INTEL_USE_NIR=1 we disable the GLSL IR cubemap normalization pass, even for vertex shaders and geometry shaders. This is wrong, but breaks a very uncommon case. When I started deleting GLSL IR for stages where we claimed to be using NIR, this bug quickly became apparent. For now, only set it for fragment shaders, and vertex shaders if brw->scalar_vs is set. Signed-off-by: Kenneth Graunke <[email protected]> Reviewed-by: Jason Ekstrand <[email protected]>
Diffstat (limited to 'progs/vp')
0 files changed, 0 insertions, 0 deletions