diff options
author | Aurelien Jarno <aurelien@aurel32.net> | 2018-01-02 09:55:48 +0100 |
---|---|---|
committer | Aurelien Jarno <aurelien@aurel32.net> | 2018-01-02 09:56:02 +0100 |
commit | 6a9dd7a7c506a215952cd355505bad5b276e42e8 (patch) | |
tree | fb397976c69b478177dae9c06f6919bd0deca885 /math/auto-libm-test-out-clog | |
parent | b05cb613e7ae507680c8d914b3e788eea782c0d6 (diff) | |
download | glibc-6a9dd7a7c506a215952cd355505bad5b276e42e8.tar.gz glibc-6a9dd7a7c506a215952cd355505bad5b276e42e8.tar.xz glibc-6a9dd7a7c506a215952cd355505bad5b276e42e8.zip |
Remove alpha specific fmax, fmin to fix sNaN handling [BZ #22660]
Various fmax and fmin function implementations mishandle sNaN arguments: (a) When both arguments are NaNs, the return value should be a qNaN, but sometimes it is an sNaN if at least one argument is an sNaN. (b) Under TS 18661-1 semantics, if either argument is an sNaN then the result should be a qNaN (whereas if one argument is a qNaN and the other is not a NaN, the result should be the non-NaN argument). Various implementations treat sNaNs like qNaNs here. One way to fix that is to detect the sNaN and add a special case. That said there is no FPU instruction to do that, so it requires transfering the FP value to an integer register and testing bits. This becomes quite complicated so it's probably better to just use the generic versions of these functions which just do that through issignaling. Changelog: [BZ #22660] * sysdeps/alpha/fpu/s_fmax.S: Remove file. * sysdeps/alpha/fpu/s_fmaxf.S: Likewise. * sysdeps/alpha/fpu/s_fmin.S: Likewise. * sysdeps/alpha/fpu/s_fminf.S: Likewise.
Diffstat (limited to 'math/auto-libm-test-out-clog')
0 files changed, 0 insertions, 0 deletions