Hi, Something that hit me in GLSL Optimizer (which is based on Mesa's GLSL). Cloning ir_loop just sets "counter" to the old counter. So in situations like:
1) loop controls are set, 2) and after that inlining happens, cloning the instructions including original variable It ends up in a situation where function body has one ir_variable object, but a loop counter there points to another ir_variable (before it was cloned). Not sure how/if that's relevant to Mesa though -- it might. I've fixed it in my tree with this: https://github.com/aras-p/glsl-optimizer/commit/c2919f69#diff-0 -- Aras Pranckevičius work: http://unity3d.com home: http://aras-p.info
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
