[Bug 100303] Adding a single, meaningless if-else to a shader source leads to different image

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Apr 8 01:25:17 UTC 2017


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

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

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

--- Comment #8 from Timothy Arceri <t_arceri at yahoo.com.au> ---
Fixed by:

commit bfabef0e7104dc4043a74ef44e71ecc7636cfe12
Author: Timothy Arceri <tarceri at itsqueeze.com>
Date:   Fri Apr 7 11:24:37 2017 +1000

    glsl: fix lower jumps for nested non-void returns

    Fixes the case were a loop contains a return and the loop is
    nested inside an if.

    Reviewed-by: Roland Scheidegger <sroland at vmware.com>
    https://bugs.freedesktop.org/show_bug.cgi?id=100303

-- 
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/20170408/893d20af/attachment.html>


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