https://bugs.freedesktop.org/show_bug.cgi?id=96765
Bug ID: 96765
Summary: BindFragDataLocationIndexed on array fragment shader
output.
Product: Mesa
Version: 11.2
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Mesa core
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
While trying to make Chromium use the 3.3 core profile of Mesa 11.2, the
following bug showed up.
When trying to use an array fragment varying variable as the secondary fragment
color (index = 0) the driver seems to decide to set it to another location
instead. Causing nothing to be rendered. The same code with non-array variables
provides the expected result.
Repro case at
https://github.com/Kangz/GLDriverBugs/blob/master/blend_func_extended_array/Main.cpp
running it shows that SecondaryFragData[0] is set to location 1 index 0 instead
of location 0 index 1.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug._______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
