summaryrefslogtreecommitdiffstats
path: root/lib/libgssapi
diff options
context:
space:
mode:
authorbde <bde@FreeBSD.org>2006-07-05 20:06:42 +0000
committerbde <bde@FreeBSD.org>2006-07-05 20:06:42 +0000
commitac26a61be9496259b14e0c20c12cc17a612c84a0 (patch)
tree567070d4c383a475c1b263006cf91556ea1e3b82 /lib/libgssapi
parentfe0b47d3f1e762a919d9c613bffd80316d8e44af (diff)
downloadFreeBSD-src-ac26a61be9496259b14e0c20c12cc17a612c84a0.zip
FreeBSD-src-ac26a61be9496259b14e0c20c12cc17a612c84a0.tar.gz
Removed the optimized asm versions of scalb() and scalbf(). These
functions are only for compatibility with obsolete standards. They shouldn't be used, so they shouldn't be optimized. Use the generic versions instead. This fixes scalbf() as a side effect. The optimized asm version left garbage on the FP stack. I fixed the corresponding bug in the optimized asm scalb() and scalbn() in 1996. NetBSD fixed it in scalb(), scalbn() and scalbnf() in 1999 but missed fixing it in scalbf(). Then in 2005 the bug was reimplemented in FreeBSD by importing NetBSD's scalbf(). The generic versions have slightly different error handling: - the asm versions blindly round the second parameter to a (floating point) integer and proceed, while the generic versions return NaN if this rounding changes the value. POSIX permits both behaviours (these functions are XSI extensions and the behaviour for a bogus non-integral second parameter is unspecified). Apart from this and the bug in scalbf(), the behaviour of the generic versions seems to be identical. (I only exhusatively tested generic_scalbf(1.0F, anyfloat) == asm_scalb(1.0F, anyfloat). This covers many representative corner cases involving NaNs and Infs but doesn't test exception flags. The brokenness of scalbf() showed up as weird behaviour after testing just 7 integer cases sequentially.)
Diffstat (limited to 'lib/libgssapi')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud