ir_variable has maximum access out of bounds -- but it's not out of bounds

Submitted by Ilia Mirkin @imirkin

Assigned to mes..@..op.org

Link to original bug (#109532)

Description

Created attachment 143274 gdb session + generated shaders

This dEQP test asserts, at least on nouveau, but I don't see what would cause it to be driver-specific.

dEQP-GLES31.functional.ssbo.layout.random.all_per_block_buffers.18

This appears to happen because it doesn't understand the interface array index properly? This message is printed before the abort:

ir_variable has maximum access out of bounds (1 vs 0)

For some reason it thinks that the array length is 1 when it should be 2. I recall interfaces being treated rather differently than most things, so perhaps related.

Attachment 143274, "gdb session + generated shaders":
file_109532.txt

Version: git