Gcc builtin review: isinf, insnan ...

Joseph Myers joseph@codesourcery.com
Fri May 29 13:30:00 GMT 2015


On Fri, 29 May 2015, Wilco Dijkstra wrote:

> so shouldn't be the default. Both GCC and GLIBC are too conservative and don't
> generate quality floating point code by default. And despite conservative and 

The very slow multiple-precision paths in some dbl-64 functions that 
attempt to be correctly rounding should simply be removed as out of scope 
for the goals of those functions, subject to error analysis showing that 
the previous paths in the code always generate results within glibc's 
accuracy goals (a few ulps).

-- 
Joseph S. Myers
joseph@codesourcery.com



More information about the Libc-alpha mailing list