summaryrefslogtreecommitdiffstats
path: root/src/mesa/Android.libmesa_st_mesa.mk
diff options
context:
space:
mode:
authorKenneth Graunke <[email protected]>2017-05-10 00:57:05 -0700
committerKenneth Graunke <[email protected]>2017-06-14 15:56:21 -0700
commit3d34e275224689c4782f0aa3eada90146b3406a0 (patch)
treee9349f615869ae4191bbf5c889bb10ce606ee00c /src/mesa/Android.libmesa_st_mesa.mk
parentd9261275cc1328d6a30e19b92db21df23adf7219 (diff)
i965: Make Gen4-5 SF_STATE use the point size calculations from Gen6+.
Apparently, Nanhai made the Gen4-5 point size calculations round to the nearest integer in commit 8d5231a3582e4f2769ac0685cf0174e09750700e, "according to spec". When Eric first ported the driver to Sandybridge, he did not implement this rounding. In the GL 2.1 and 3.0 specs "Basic Point Rasterization" section, it does say "If antialiasing and point sprites are disabled, the actual width is determined by rounding the supplied width to the nearest integer, then clamping it to the implementation-dependent maximum non-antialised point width." In contrast, GL 3.1 and later do not appear to contain this rounding. It might be reasonable to round, given that we only implement GL 2.1. Of course, if we were to do that, we should actually implement the AA vs. non-AA distinction. Brian added an XXX comment reminding us to fix this 10 years ago, but it never happened. I think a better plan is to follow the newer, unrounded behavior. This is what we do on Gen6+ and it passes all the relevant conformance tests. Reviewed-by: Rafael Antognolli <[email protected]>
Diffstat (limited to 'src/mesa/Android.libmesa_st_mesa.mk')
0 files changed, 0 insertions, 0 deletions