<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - BindFragDataLocationIndexed on array fragment shader output." href="https://bugs.freedesktop.org/show_bug.cgi?id=96765#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - BindFragDataLocationIndexed on array fragment shader output." href="https://bugs.freedesktop.org/show_bug.cgi?id=96765">bug 96765</a> from <a class="email" href="mailto:corentin@wallez.net" title="Corentin Wallez <corentin@wallez.net>"> Corentin Wallez</a> <pre>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 <a href="https://cvs.khronos.org/bugzilla/show_bug.cgi?id=7829">https://cvs.khronos.org/bugzilla/show_bug.cgi?id=7829</a> 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>