aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2015-09-30 23:34:59 +0000
committerJoseph Myers <joseph@codesourcery.com>2015-09-30 23:34:59 +0000
commit7cda516f5f23772fd37ca3a5e018fca5bf388435 (patch)
tree1a344d2d855f73e86ac7d9e056ea6e08f24ad777 /README
parent8c6c9236361fbc077769673c259828216403bc33 (diff)
downloadglibc-7cda516f5f23772fd37ca3a5e018fca5bf388435.zip
glibc-7cda516f5f23772fd37ca3a5e018fca5bf388435.tar.gz
glibc-7cda516f5f23772fd37ca3a5e018fca5bf388435.tar.bz2
Fix ldbl-128ibm exp10l spurious overflows (bug 16620).
The ldbl-128ibm implementation of exp10l uses a version of log(10) split into high and low parts - but the low part is negative, so causing spurious overflows from __ieee754_expl (exp_high) in cases close to the overflow threshold (I added relevant tests close to the overflow threshold to the testsuite earlier today). The same issue applies close to the underflow threshold as well (except that spurious underflows in IBM long double arithmetic are harder to fix than the other deficiencies, so we might end up permitting those for IBM long double in the libm testsuite, as permitted by ISO C). This patch fixes it to use a low part rounded downward to 48 bits instead. (The choice of 48 instead of 53 bits is to make it more obviously safe even when the low part of the argument is negative.) Tested for powerpc. (Note that because of libgcc bugs with multiplication very close to LDBL_MAX, libgcc also needs patching for all the problem cases to be fixed, but this patch is still safe and correct in the absence of such libgcc fixes.) [BZ #16620] * sysdeps/ieee754/ldbl-128ibm/e_exp10l.c (log10_high): Use value of log (10) rounded downward to 48 bits. (log10_low): Use corresponding low part of log (10).
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions