freedreno/ir3: Apply the max upload limit to initial range setup
authorEric Anholt <eric@anholt.net>
Fri, 4 Sep 2020 17:59:37 +0000 (10:59 -0700)
committerMarge Bot <eric+marge@anholt.net>
Tue, 8 Sep 2020 18:20:51 +0000 (18:20 +0000)
commit41b5aafef341f8086be16901c15d4325a3be3359
tree248905d664331d7b3d11afbea39b2fcbc1f6ff51
parentf74c3b0404c21568ec3621aad28f450c788ebfd4
freedreno/ir3: Apply the max upload limit to initial range setup

There's no sense in planning out an upload that we won't be able to
actually upload due to the limit.  This means that we can keep making
other loads pushable, even after we find one that wouldn't be, and we
don't fill the const file with UBO data for a load we couldn't promote.

total instructions in shared programs: 8096655 -> 8044344 (-0.65%)
total constlen in shared programs: 1447824 -> 1411384 (-2.52%)
total cat6 in shared programs: 97824 -> 89983 (-8.02%)

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6359>
src/freedreno/ir3/ir3_nir_analyze_ubo_ranges.c