[Mesa-dev] [PATCH 2/5] ra: Delete the conflict lists in ra_set_finalize
eric at anholt.net
Mon Aug 3 18:12:34 PDT 2015
Jason Ekstrand <jason at 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?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 818 bytes
Desc: not available
More information about the mesa-dev