diff options
author | Vincent Lefevre <vincent@vinc17.net> | 2024-11-22 13:54:53 -0300 |
---|---|---|
committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2024-11-25 09:20:47 -0300 |
commit | 68d71289425bb133c6cbf0f5065da6b1d99f81fc (patch) | |
tree | 87bf881cae7c1a7d986ba455d88a2709f29cf6fa /malloc/reallocarray.c | |
parent | c621d4f74fcbb69818125b5ef128937a72f64888 (diff) | |
download | glibc-68d71289425bb133c6cbf0f5065da6b1d99f81fc.zip glibc-68d71289425bb133c6cbf0f5065da6b1d99f81fc.tar.gz glibc-68d71289425bb133c6cbf0f5065da6b1d99f81fc.tar.bz2 |
math: Fix non-portability in the computation of signgam in lgammaf
The k>>31 in signgam = 1 - (((k&(k>>31))&1)<<1); is not portable:
* The ISO C standard says "If E1 has a signed type and a negative
value, the resulting value is implementation-defined." (this is
still in C23).
* If the int type is larger than 32 bits (e.g. a 64-bit type),
then k = INT_MAX; line 144 will make k>>31 put 1 in bit 0
(thus signgam will be -1) while 0 is expected.
Moreover, instead of the fx >= 0x1p31f condition, testing fx >= 0
is probably better for 2 reasons:
The signgam expression has more or less a condition on the sign
of fx (the goal of k>>31, which can be dropped with this new
condition). Since fx ≥ 0 should be the most common case, one can
get signgam directly in this case (value 1). And this simplifies
the expression for the other case (fx < 0).
This new condition may be easier/faster to test on the processor
(e.g. by avoiding a load of a constant from the memory).
This is commit d41459c731865516318f813cf4c966dafa0eecbf from CORE-MATH.
Checked on x86_64-linux-gnu.
Diffstat (limited to 'malloc/reallocarray.c')
0 files changed, 0 insertions, 0 deletions