Jason Ekstrand <ja...@jlekstrand.net> writes: > I'm not 100% sure that this is the right patch. Instead of baking 256 into > the allocator, we could allow the user to pass in an initial constant. > Since the maximum is statically known, we could also make said constant a > hard limit and allocate everything up-front in a single array and save all > the allocations.
This sucks if we don't have enormous reg sets. But we don't use the conflict_list if you're precomputing the q_values, right? Maybe flag that we don't need conflict lists at all at reg_set creation time?
signature.asc
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev