summaryrefslogtreecommitdiff
path: root/src/thread/syscall_cp.c
diff options
context:
space:
mode:
authorSzabolcs Nagy <nsz@port70.net>2014-10-29 00:25:50 +0100
committerRich Felker <dalias@aerifal.cx>2014-10-31 11:35:40 -0400
commit79ca86094d70f43252b683c3a3ccb572d462cf28 (patch)
tree3396f9fcd33336c7cecb24399e716c407077acab /src/thread/syscall_cp.c
parent2da3ab1382ca8e39eb1e4428103764a81fba73d3 (diff)
downloadmusl-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 'src/thread/syscall_cp.c')
0 files changed, 0 insertions, 0 deletions