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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Corentin Wallez <corentin at wallez.net> ---
Thanks for taking a look, indeed my understanding was wrong but I found a
Khronos bug related to this that doesn't have a formal resolution but indicates
that while you can't bind array elements individually, "array[0]" should be
equivalent to "array". See
https://cvs.khronos.org/bugzilla/show_bug.cgi?id=7829

Unfortunately Chrome has been testing this on few platforms, so far it only
tested NVIDIA proprietary (passes), fglrx (doesn't pass). It also fails on the
OSX drivers, seemingly for the same reason as for Mesa it seems.

Given all the above, I will fix Chromium's tests to not use indices, can you
still consider making the [0] equivalent to no subscript?

Thank you for your time.

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