This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug math/22660] fmax, fmin sNaN handling on alpha
- From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 02 Jan 2018 08:57:34 +0000
- Subject: [Bug math/22660] fmax, fmin sNaN handling on alpha
- Auto-submitted: auto-generated
- References: <bug-22660-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22660
--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, master has been updated
via 6a9dd7a7c506a215952cd355505bad5b276e42e8 (commit)
from b05cb613e7ae507680c8d914b3e788eea782c0d6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6a9dd7a7c506a215952cd355505bad5b276e42e8
commit 6a9dd7a7c506a215952cd355505bad5b276e42e8
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Tue Jan 2 09:55:48 2018 +0100
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.
-----------------------------------------------------------------------
Summary of changes:
ChangeLog | 8 ++++++
sysdeps/alpha/fpu/s_fmax.S | 52 -------------------------------------------
sysdeps/alpha/fpu/s_fmaxf.S | 1 -
sysdeps/alpha/fpu/s_fmin.S | 52 -------------------------------------------
sysdeps/alpha/fpu/s_fminf.S | 1 -
5 files changed, 8 insertions(+), 106 deletions(-)
delete mode 100644 sysdeps/alpha/fpu/s_fmax.S
delete mode 100644 sysdeps/alpha/fpu/s_fmaxf.S
delete mode 100644 sysdeps/alpha/fpu/s_fmin.S
delete mode 100644 sysdeps/alpha/fpu/s_fminf.S
--
You are receiving this mail because:
You are on the CC list for the bug.