Argh, this is exactly what I had in mind and I did it with
_mesa_longest_attribute_name_length but forgot it in
_mesa_count_active_attribs ... many thanks for catching this. I agree on
the assertion change, that is simple and will make these bugs much
easier to catch.
My overall plan is to
It's returning random values, because RESOURCE_VAR() is casting
different objects into ir_variable pointers.
This updates _mesa_count_active_attribs to filters the resources with
the same logic used in _mesa_longest_attribute_name_length.
https://bugs.freedesktop.org/show_bug.cgi?id=90207
P.S.: