summaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/i965/brw_vec4_nir.cpp
diff options
context:
space:
mode:
authorJason Ekstrand <jason.ekstrand@intel.com>2016-07-18 18:46:43 -0700
committerJason Ekstrand <jason.ekstrand@intel.com>2016-07-20 08:18:19 -0700
commitd4d505d0b04b9bce7c346fe0710df9921861edd6 (patch)
treeebef937438be270fb5463bd8cf217e6ad7cdf044 /src/mesa/drivers/dri/i965/brw_vec4_nir.cpp
parent27ef7bfd6cd2d960844f4c79d6dddc0bda0b20b0 (diff)
downloadexternal_mesa3d-d4d505d0b04b9bce7c346fe0710df9921861edd6.zip
external_mesa3d-d4d505d0b04b9bce7c346fe0710df9921861edd6.tar.gz
external_mesa3d-d4d505d0b04b9bce7c346fe0710df9921861edd6.tar.bz2
i965/miptree: Enforce that height == 1 for 1-D array textures
The GL API and mesa internals do this differently than we do. In GL, there is no depth parameter for 1-D arrays and height is used. In the i965 miptree code we do the sane thing and make height == 1 and use depth for number of slices. This makes for a mismatch every time we create a 1-D array texture from GL. Instead of actually solving this problem, we just said "1-D is hard, let's make sure it works no matter which way we pass the parameters" and called it a day. This commit fixes the one GL -> i965 transition point where we weren't already handling 1-D array textures to do the right thing and then replaces the magic fixup code with an assert that you're doing the right thing. Signed-off-by: Jason Ekstrand <jason@jlekstrand.net> Reviewed-by: Iago Toral Quiroga <itoral@igalia.com> Reviewed-by: Chris Forbes <chrisforbes@google.com> Cc: "12.0 11.2 11.1" <mesa-stable@lists.freedesktop.org>
Diffstat (limited to 'src/mesa/drivers/dri/i965/brw_vec4_nir.cpp')
0 files changed, 0 insertions, 0 deletions