Hi! On Fri, Jun 24, 2022 at 10:02:19AM +0800, HAO CHEN GUI wrote: > This patch also binds __builtin_vsx_xs[min/max]dp to fmin/max instead > of smin/max. So the builtins always generate xs[min/max]dp on all > platforms.
But how does this not blow up with -ffast-math? In the other direction I am worried that the unspecs will degrade performance (relative to smin/smax) when -ffast-math *is* active (and this new builtin code and pattern doesn't blow up). I still think we should get RTL codes for this, to have access to proper floating point min/max semantics always and everywhere. "fmin" and "fmax" seem to be good names :-) Segher
