[Mesa-dev] [Bug 96765] BindFragDataLocationIndexed on array fragment shader output.

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Jul 7 00:23:50 UTC 2016


--- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> ---

This patch should also fix it for the [0] names. I chose to implement it as a
fallback thing, so if you have foo and foo[0] set, foo will always get picked,
no matter which was set first.

If I stripped the [0]'s at bind time, one might run into the issue of a

out vec4 foo;

shader (which, as the spec says, can be added after the binding is done on the
program), and someone doing a bind on both foo and foo[0], and it'd be awkward
for the foo[0] to win out in that case.

You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160707/9c445c72/attachment-0001.html>

More information about the mesa-dev mailing list