2004-01-18 10:32:49 +00:00
|
|
|
/*-
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
* Copyright (c) 2004-2008 David Schultz <das@FreeBSD.ORG>
|
2004-01-18 10:32:49 +00:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <sys/cdefs.h>
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
|
|
|
#include <float.h>
|
|
|
|
#include <limits.h>
|
|
|
|
#include <math.h>
|
|
|
|
#include "fpmath.h"
|
|
|
|
#include "gdtoaimp.h"
|
|
|
|
|
|
|
|
/* Strings values used by dtoa() */
|
|
|
|
#define INFSTR "Infinity"
|
|
|
|
#define NANSTR "NaN"
|
|
|
|
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
#define DBL_ADJ (DBL_MAX_EXP - 2)
|
|
|
|
#define SIGFIGS ((DBL_MANT_DIG + 3) / 4 + 1)
|
2004-01-18 10:32:49 +00:00
|
|
|
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
static const float one[] = { 1.0f, -1.0f };
|
2004-01-18 10:32:49 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* This procedure converts a double-precision number in IEEE format
|
|
|
|
* into a string of hexadecimal digits and an exponent of 2. Its
|
|
|
|
* behavior is bug-for-bug compatible with dtoa() in mode 2, with the
|
|
|
|
* following exceptions:
|
|
|
|
*
|
|
|
|
* - An ndigits < 0 causes it to use as many digits as necessary to
|
|
|
|
* represent the number exactly.
|
|
|
|
* - The additional xdigs argument should point to either the string
|
|
|
|
* "0123456789ABCDEF" or the string "0123456789abcdef", depending on
|
|
|
|
* which case is desired.
|
|
|
|
* - This routine does not repeat dtoa's mistake of setting decpt
|
|
|
|
* to 9999 in the case of an infinity or NaN. INT_MAX is used
|
|
|
|
* for this purpose instead.
|
|
|
|
*
|
|
|
|
* Note that the C99 standard does not specify what the leading digit
|
|
|
|
* should be for non-zero numbers. For instance, 0x1.3p3 is the same
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
* as 0x2.6p2 is the same as 0x4.cp3. This implementation always makes
|
|
|
|
* the leading digit a 1. This ensures that the exponent printed is the
|
|
|
|
* actual base-2 exponent, i.e., ilogb(d).
|
2004-01-18 10:32:49 +00:00
|
|
|
*
|
|
|
|
* Inputs: d, xdigs, ndigits
|
|
|
|
* Outputs: decpt, sign, rve
|
|
|
|
*/
|
|
|
|
char *
|
|
|
|
__hdtoa(double d, const char *xdigs, int ndigits, int *decpt, int *sign,
|
|
|
|
char **rve)
|
|
|
|
{
|
|
|
|
union IEEEd2bits u;
|
|
|
|
char *s, *s0;
|
|
|
|
int bufsize;
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
uint32_t manh, manl;
|
2004-01-18 10:32:49 +00:00
|
|
|
|
|
|
|
u.d = d;
|
|
|
|
*sign = u.bits.sign;
|
|
|
|
|
|
|
|
switch (fpclassify(d)) {
|
|
|
|
case FP_NORMAL:
|
2005-01-18 18:44:07 +00:00
|
|
|
*decpt = u.bits.exp - DBL_ADJ;
|
2004-01-18 10:32:49 +00:00
|
|
|
break;
|
|
|
|
case FP_ZERO:
|
|
|
|
*decpt = 1;
|
|
|
|
return (nrv_alloc("0", rve, 1));
|
|
|
|
case FP_SUBNORMAL:
|
2005-01-18 18:44:07 +00:00
|
|
|
u.d *= 0x1p514;
|
|
|
|
*decpt = u.bits.exp - (514 + DBL_ADJ);
|
2004-01-18 10:32:49 +00:00
|
|
|
break;
|
|
|
|
case FP_INFINITE:
|
|
|
|
*decpt = INT_MAX;
|
|
|
|
return (nrv_alloc(INFSTR, rve, sizeof(INFSTR) - 1));
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
default: /* FP_NAN or unrecognized */
|
2004-01-18 10:32:49 +00:00
|
|
|
*decpt = INT_MAX;
|
|
|
|
return (nrv_alloc(NANSTR, rve, sizeof(NANSTR) - 1));
|
|
|
|
}
|
|
|
|
|
|
|
|
/* FP_NORMAL or FP_SUBNORMAL */
|
|
|
|
|
|
|
|
if (ndigits == 0) /* dtoa() compatibility */
|
|
|
|
ndigits = 1;
|
|
|
|
|
|
|
|
/*
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
* If ndigits < 0, we are expected to auto-size, so we allocate
|
|
|
|
* enough space for all the digits.
|
2004-01-18 10:32:49 +00:00
|
|
|
*/
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
bufsize = (ndigits > 0) ? ndigits : SIGFIGS;
|
2004-01-18 10:32:49 +00:00
|
|
|
s0 = rv_alloc(bufsize);
|
|
|
|
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
/* Round to the desired number of digits. */
|
|
|
|
if (SIGFIGS > ndigits && ndigits > 0) {
|
|
|
|
float redux = one[u.bits.sign];
|
|
|
|
int offset = 4 * ndigits + DBL_MAX_EXP - 4 - DBL_MANT_DIG;
|
|
|
|
u.bits.exp = offset;
|
|
|
|
u.d += redux;
|
|
|
|
u.d -= redux;
|
|
|
|
*decpt += u.bits.exp - offset;
|
2004-01-18 10:32:49 +00:00
|
|
|
}
|
|
|
|
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
manh = u.bits.manh;
|
|
|
|
manl = u.bits.manl;
|
|
|
|
*s0 = '1';
|
|
|
|
for (s = s0 + 1; s < s0 + bufsize; s++) {
|
|
|
|
*s = xdigs[(manh >> (DBL_MANH_SIZE - 4)) & 0xf];
|
|
|
|
manh = (manh << 4) | (manl >> (DBL_MANL_SIZE - 4));
|
|
|
|
manl <<= 4;
|
2004-01-18 10:32:49 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* If ndigits < 0, we are expected to auto-size the precision. */
|
|
|
|
if (ndigits < 0) {
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
for (ndigits = SIGFIGS; s0[ndigits - 1] == '0'; ndigits--)
|
2004-01-18 10:32:49 +00:00
|
|
|
;
|
|
|
|
}
|
|
|
|
|
|
|
|
s = s0 + ndigits;
|
Make several changes to the way printf handles hex floating point (%a):
1. Previously, printing the number 1.0 could produce 0x1p+0, 0x2p-1,
0x4p-2, or 0x8p-3, depending on what happened to be convenient. This
meant that printing a value as a double and printing the same value
as a long double could produce different (but equivalent) results.
The change is to always make the leading digit a 1, unless the
number is 0. This solves the aforementioned problem and has
several other advantages.
2. Use the FPU to do rounding. This is far simpler and more portable
than manipulating the bits, and it fixes an obsure round-to-even
bug. It also raises the exceptions now required by IEEE 754R.
The drawbacks are that it is usually slightly slower, and it makes
printf less effective as a debugging tool when the FPU is hosed
(e.g., due to a buggy softfloat implementation).
3. On i386, twiddle the rounding precision so that (2) works properly
for long doubles.
4. Make several simplifications that are now possible due to (2).
5. Split __hldtoa() into a separate file.
Thanks to remko for access to a sparc64 box for testing.
2008-04-12 03:11:36 +00:00
|
|
|
*s = '\0';
|
2004-01-18 10:32:49 +00:00
|
|
|
if (rve != NULL)
|
|
|
|
*rve = s;
|
|
|
|
return (s0);
|
|
|
|
}
|