[Bug 93336] [IVB,HSW] piglit.spec.arb_program_interface_query.arb_program_interface_query-getprogramresourceiv crashes

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=93336

--- Comment #1 from Alejandro Piñeiro (freenode IRC: apinheiro) <apinheiro at igalia.com> ---
I took a brief look to this one. Two quick notes.

(In reply to Mark Janes from comment #0)

> Failed to compile compute shader: 0:9(8): error: unrecognized layout
> identifier `size4x32'

<skip>

> uniform cs_uniform_block {
> 	uniform vec4 cs_test;
> };
> layout(size4x32) uniform image2D tex;

Using "layout(rgba32f)" gets the shader being compiled without problem, and the
subtest passing (the test itself still fails). After a skim reading on
EXT_shader_image_load_store and ARB_shader_image_load_store (the latter depends
on the former), that layout should be allowed, and it is also more general (for
example, using rgba32i fails due a format mismatch). So I suspect that this is
a bug on the implementation for those extensions. The problem was hidden until
now because this shader needed compute shader.

Using glslangValidator with that shader also prints a "unrecognized layout
identifier". Having said so, it prints several other errors.

NVIDIA proprietary drivers handle that shader without problems (as pointed on
the commit log of those tests)

Will keep investigating to check if the problem is in the shader. In that case,
the bug would be on the piglit test.

> subroutine vec4 com_offset();
> subroutine uniform com_offset COMPUTE;
> subroutine (com_offset) vec4 css() { return vec4(1, 0, 0, 0); }
> void main() {
> 	imageStore(tex, ivec2(0.0), cs_test + COMPUTE());
> }


Second note:
piglit.spec.arb_program_interface_query.arb_program_interface_query-resource-location
is affected by the same problem, that got also fixed by changing size4x32 for
rgba32f.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160211/3c51aad0/attachment.html>