[Mesa-dev] glsl: IR clone of ir_loop doesn't remap variable reference
aras at unity3d.com
Tue Dec 18 03:47:32 PST 2012
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
1) loop controls are set,
2) and after that inlining happens, cloning the instructions including
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
Not sure how/if that's relevant to Mesa though -- it might. I've fixed it
in my tree with this:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mesa-dev