Re: [PATCH, libquadmath]: Use built-in functions instead of fabsq, copysignq and nanq.

2016-06-14 Thread Joseph Myers
On Tue, 14 Jun 2016, Jakub Jelinek wrote: > Couldn't you instead add into a header inline functions or macros > that map fabsq to __builtin_fabsq etc.? Then you could keep the *.c > files as is. > What I don't really like on the patch is that it diverges too much from the > original libc sources

Re: [PATCH, libquadmath]: Use built-in functions instead of fabsq, copysignq and nanq.

2016-06-13 Thread Jakub Jelinek
On Sun, Jun 12, 2016 at 11:50:11PM +0200, Uros Bizjak wrote: > Attached (mostly mechanical) patch uses equivalent built-in functions > for fabsq, copysignq and nanq. The patch allows more aggressive > compiler optimizations, where for fabsq and copysignq, the compiler > will emit 128bit SSE bitops,

[PATCH, libquadmath]: Use built-in functions instead of fabsq, copysignq and nanq.

2016-06-12 Thread Uros Bizjak
Hello! Attached (mostly mechanical) patch uses equivalent built-in functions for fabsq, copysignq and nanq. The patch allows more aggressive compiler optimizations, where for fabsq and copysignq, the compiler will emit 128bit SSE bitops, and a 128bit constant load instead of nanq function call. T