Re:Don't "optimize" conditional moves in shaders with mix()+...
by Dylan16807 on Friday February 14, 2025 @02:10PM
(#43051902)
But do you want /width*width to be optimized? Or associative and commutative operations in general? Then you have to reject the opposite opinion.
[ Parent
| on HN ]
Re:Don't "optimize" conditional moves in shaders with mix()+...
by chrisjj on Sunday February 16, 2025 @04:13PM
(#43071770)
[delayed]
Re:Don't "optimize" conditional moves in shaders with mix()+...
by Dylan16807 on Tuesday February 18, 2025 @10:08PM
(#43098122)
Changes like that will break just as much code as adding extra precision will. Because it will change how things round, and not much else, just like adding extra precision. They're both slightly disruptive, and they tend to disrupt the same kind of thing, unlike removing precision which is very disruptive all over.