[Bug 93339] glLinkProgram() should fail when a varying is never written to in a previous stage

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 16 00:27:57 UTC 2016


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

Timothy Arceri <t_arceri at yahoo.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Timothy Arceri <t_arceri at yahoo.com.au> ---
(In reply to Mark Janes from comment #6)
> Is there a piglit test for this functionality?

The bug title is wrong we shouldn't fail to link in this case. The Mesa change
is to warn in GL as well as ES which we already do. As for failing in version
1.20 and below there could be a test in the /shaders dumping ground I had a
quick look but couldn't find anything obvious.

Fixed by:

commit    00a1bd13b5c6b565b5d15409a6f814b0df2fbe29
glsl: warn in GL as well as ES when varying not written

Reviewed-by: Iago Toral Quiroga <itoral at igalia.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93339

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160216/919e1709/attachment.html>


More information about the intel-3d-bugs mailing list