summaryrefslogtreecommitdiff
path: root/src/gallium/drivers/r600/Android.mk
diff options
context:
space:
mode:
authorKenneth Graunke <kenneth@whitecape.org>2017-10-10 01:02:44 -0700
committerKenneth Graunke <kenneth@whitecape.org>2017-10-10 17:29:37 -0700
commit6f5abf31466aedd63234aa318f8d2d0e4cb35570 (patch)
tree4bf705a2fad1af5d36a7d21e675e055fdaf73fcf /src/gallium/drivers/r600/Android.mk
parent2d36efdb7f18f061c519dbb93f6058bf161aad33 (diff)
i965: Fix output register sizes when multiple variables share a slot.
ARB_enhanced_layouts allows multiple output variables to share the same location - and these variables may not have the same sizes. For example, consider these output variables: // consume X/Y/Z components of 6 vectors layout(location = 0) out vec3 a[6]; // consumes W component of the first vector layout(location = 0, component = 3) out float b; Looking at the first declaration, we see that VARYING_SLOT_VAR0 needs 24 components worth of space (vec3 padded out to a vec4, 4 * 6 = 24). But looking at the second declaration, we would think that VARYING_SLOT_VAR0 needs only 4 components of space (a single float padded out to a vec4). nir_setup_outputs() only considered the space requirements of the first declaration it happened to see, so if 'float b' came first, it would underallocate the output register space, causing brw_fs_validator.cpp to assert fail about inst->dst.offset exceeding the register size. Fixes Piglit's tests/spec/arb_enhanced_layouts/execution/component-layout/ vs-to-fs-array-interleave-single-location.shader_test. Thanks to Tim Arceri for finding this bug and writing a test! Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
Diffstat (limited to 'src/gallium/drivers/r600/Android.mk')
0 files changed, 0 insertions, 0 deletions