ir_variable has maximum access out of bounds -- but it's not out of bounds
Submitted by Ilia Mirkin
Assigned to mes..@..op.org
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.
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":