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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jul 1 17:04:59 UTC 2016


            Bug ID: 96765
           Summary: BindFragDataLocationIndexed on array fragment shader
           Product: Mesa
           Version: 11.2
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Mesa core
          Assignee: mesa-dev at lists.freedesktop.org
          Reporter: corentin at wallez.net
        QA Contact: mesa-dev at lists.freedesktop.org

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
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160701/2d8dc7a2/attachment.html>

More information about the mesa-dev mailing list