diff options
author | Szabolcs Nagy <nsz@port70.net> | 2014-10-29 00:25:50 +0100 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2014-10-31 11:35:40 -0400 |
commit | 79ca86094d70f43252b683c3a3ccb572d462cf28 (patch) | |
tree | 3396f9fcd33336c7cecb24399e716c407077acab /VERSION | |
parent | 2da3ab1382ca8e39eb1e4428103764a81fba73d3 (diff) | |
download | musl-79ca86094d70f43252b683c3a3ccb572d462cf28.tar.gz musl-79ca86094d70f43252b683c3a3ccb572d462cf28.tar.bz2 musl-79ca86094d70f43252b683c3a3ccb572d462cf28.tar.xz musl-79ca86094d70f43252b683c3a3ccb572d462cf28.zip |
fix rint.c and rintf.c when FLT_EVAL_METHOD!=0
The old code used the rounding idiom incorrectly:
y = (double)(x + 0x1p52) - 0x1p52;
the cast is useless if FLT_EVAL_METHOD==0 and causes a second rounding
if FLT_EVAL_METHOD==2 which can give incorrect result in nearest rounding
mode, so the correct idiom is to add/sub a power-of-2 according to the
characteristics of double_t.
This did not cause actual bug because only i386 is affected where rint
is implemented in asm.
Other rounding functions use a similar idiom, but they give correct
results because they only rely on getting a neighboring integer result
and the rounding direction is fixed up separately independently of the
current rounding mode. However they should be fixed to use the idiom
correctly too.
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions