[Bug 105731] linker error "fragment shader input ... has no matching output in the previous stage" when previous stage's output declaration in a separate shader object

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 30 01:00:11 UTC 2018


--- Comment #4 from Timothy Arceri <t_arceri at yahoo.com.au> ---
(In reply to Mark Janes from comment #3)
> Vadym, can you make a piglit test for this bug?

Hi Mark, this was already done :)

commit c98669cbd1f801c8fda25aceab23b5c54de76b9e
Author: Vadym Shovkoplias <vadim.shovkoplias at gmail.com>
Date:   Mon Aug 27 15:19:40 2018 +0300

    glsl-1.30: add linker test for inter stage in/out vars usage

    This test exposes a Mesa GLSL linker bug. The test fails with the
    following error message:

       error: fragment shader input `foo' has no matching output in the

    Signed-off-by: Vadym Shovkoplias <vadym.shovkoplias at globallogic.com>
    Reviewed-by: Timothy Arceri <tarceri at itsqueeze.com>
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105731

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/20180830/80a0c3bc/attachment.html>

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