[Bug 101378] interpolateAtSample check for input parameter is too strict

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Jun 11 09:41:00 UTC 2017


--- Comment #1 from freedesktop at ca.sh13.net ---
Sorry, copy/paste error, the first two lines are from another unrelated error.
The correct error message is just this part:

    0:18(33): error: parameter `interpolant` must be a shader input
    0:18(6): error: no matching function for call to `length(error)';
candidates are:
    0:18(6): error:    float length(float)
    0:18(6): error:    float length(vec2)
    0:18(6): error:    float length(vec3)
    0:18(6): error:    float length(vec4)
    0:18(6): error:    double length(double)
    0:18(6): error:    double length(dvec2)
    0:18(6): error:    double length(dvec3)
    0:18(6): error:    double length(dvec4)
    0:18(6): error: operands to relational operators must be scalar and numeric
    0:18(6): error: if-statement condition must be scalar boolean

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/20170611/db3c3dad/attachment.html>

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