IEEE 754-1985 was an industry standard for representing floating-point numbers in computers, officially adopted in 1985 and superseded in 2008 by IEEE 754-2008. During its 23 years, it was the most widely used format for floating-point computation. It was implemented in software, in the form of floating-point libraries, and in hardware, in the instructions of many CPUs and FPUs. The first integrated circuit to implement the draft of what was to become IEEE 754-1985 was the Intel 8087.
IEEE 754-1985 represents numbers in binary, providing definitions for four levels of precision, of which the two most commonly used are:
|Level||Width||Range at full precision||Precision[a]|
|Single precision||32 bits||±1.18×10−38 to ±3.4×1038||Approximately 7 decimal digits|
|Double precision||64 bits||±2.23×10−308 to ±1.80×10308||Approximately 16 decimal digits|
The standard also defines representations for positive and negative infinity, a "negative zero", five exceptions to handle invalid results like division by zero, special values called NaNs for representing those exceptions, denormal numbers to represent numbers smaller than shown above, and four rounding modes.
Representation of numbersEdit
The decimal number 0.1562510 represented in binary is 0.001012 (that is, 1/8 + 1/32). (Subscripts indicate the number base.) Analogous to scientific notation, where numbers are written to have a single non-zero digit to the left of the decimal point, we rewrite this number so it has a single 1 bit to the left of the "binary point". We simply multiply by the appropriate power of 2 to compensate for shifting the bits left by three positions:
Now we can read off the fraction and the exponent: the fraction is .012 and the exponent is −3.
As illustrated in the pictures, the three fields in the IEEE 754 representation of this number are:
- sign = 0, because the number is positive. (1 indicates negative.)
- biased exponent = −3 + the "bias". In single precision, the bias is 127, so in this example the biased exponent is 124; in double precision, the bias is 1023, so the biased exponent in this example is 1020.
- fraction = .01000…2.
IEEE 754 adds a bias to the exponent so that numbers can in many cases be compared conveniently by the same hardware that compares signed 2's-complement integers. Using a biased exponent, the lesser of two positive floating-point numbers will come out "less than" the greater following the same ordering as for sign and magnitude integers. If two floating-point numbers have different signs, the sign-and-magnitude comparison also works with biased exponents. However, if both biased-exponent floating-point numbers are negative, then the ordering must be reversed. If the exponent were represented as, say, a 2's-complement number, comparison to see which of two numbers is greater would not be as convenient.
The leading 1 bit is omitted since all numbers except zero start with a leading 1; the leading 1 is implicit and doesn't actually need to be stored which gives an extra bit of precision for "free."
The number zero is represented specially:
The number representations described above are called normalized, meaning that the implicit leading binary digit is a 1. To reduce the loss of precision when an underflow occurs, IEEE 754 includes the ability to represent fractions smaller than are possible in the normalized representation, by making the implicit leading digit a 0. Such numbers are called denormal. They don't include as many significant digits as a normalized number, but they enable a gradual loss of precision when the result of an arithmetic operation is not exactly zero but is too close to zero to be represented by a normalized number.
A denormal number is represented with a biased exponent of all 0 bits, which represents an exponent of −126 in single precision (not −127), or −1022 in double precision (not −1023). In contrast, the smallest biased exponent representing a normal number is 1 (see examples below).
Representation of non-numbersEdit
The biased-exponent field is filled with all 1 bits to indicate either infinity or an invalid result of a computation.
Positive and negative infinityEdit
Positive and negative infinity are represented thus:
- sign = 0 for positive infinity, 1 for negative infinity.
- biased exponent = all 1 bits.
- fraction = all 0 bits.
Some operations of floating-point arithmetic are invalid, such as taking the square root of a negative number. The act of reaching an invalid result is called a floating-point exception. An exceptional result is represented by a special code called a NaN, for "Not a Number". All NaNs in IEEE 754-1985 have this format:
- sign = either 0 or 1.
- biased exponent = all 1 bits.
- fraction = anything except all 0 bits (since all 0 bits represents infinity).
Range and precisionEdit
Precision is defined as the minimum difference between two successive mantissa representations; thus it is a function only in the mantissa; while the gap is defined as the difference between two successive numbers.
Single-precision numbers occupy 32 bits. In single precision:
- The positive and negative numbers closest to zero (represented by the denormalized value with all 0s in the exponent field and the binary value 1 in the fraction field) are
- ±2−23 × 2−126 ≈ ±1.40130×10−45
- The positive and negative normalized numbers closest to zero (represented with the binary value 1 in the exponent field and 0 in the fraction field) are
- ±1 × 2−126 ≈ ±1.17549×10−38
- The finite positive and finite negative numbers furthest from zero (represented by the value with 254 in the exponent field and all 1s in the fraction field) are
- ±(2−2−23) × 2127 ≈ ±3.40282×1038
Some example range and gap values for given exponents in single precision:
|Actual Exponent (unbiased)||Exp (biased)||Minimum||Maximum||Gap|
|−1||126||0.5||≈ 0.999999940395||≈ 5.96046e-8|
|0||127||1||≈ 1.999999880791||≈ 1.19209e-7|
|1||128||2||≈ 3.999999761581||≈ 2.38419e-7|
|2||129||4||≈ 7.999999523163||≈ 4.76837e-7|
|10||137||1024||≈ 2047.999877930||≈ 1.22070e-4|
|11||138||2048||≈ 4095.999755859||≈ 2.44141e-4|
|127||254||≈ 1.70141e38||≈ 3.40282e38||≈ 2.02824e31|
As an example, 16,777,217 cannot be encoded as a 32-bit float as it will be rounded to 16,777,216. This shows why floating point arithmetic is unsuitable for accounting software. However, all integers within the representable range that are a power of 2 can be stored in a 32-bit float without rounding.
Double-precision numbers occupy 64 bits. In double precision:
- The positive and negative numbers closest to zero (represented by the denormalized value with all 0s in the Exp field and the binary value 1 in the Fraction field) are
- ±2−52 × 2−1022 ≈ ±4.94066×10−324
- The positive and negative normalized numbers closest to zero (represented with the binary value 1 in the Exp field and 0 in the fraction field) are
- ±1 × 2−1022 ≈ ±2.22507×10−308
- The finite positive and finite negative numbers furthest from zero (represented by the value with 2046 in the Exp field and all 1s in the fraction field) are
- ±(2−2−52) × 21023 ≈ ±1.79769×10308
Some example range and gap values for given exponents in double precision:
|Actual Exponent (unbiased)||Exp (biased)||Minimum||Maximum||Gap|
|−1||1022||0.5||≈ 0.999999999999999888978||≈ 1.11022e-16|
|0||1023||1||≈ 1.999999999999999777955||≈ 2.22045e-16|
|1||1024||2||≈ 3.999999999999999555911||≈ 4.44089e-16|
|2||1025||4||≈ 7.999999999999999111822||≈ 8.88178e-16|
|10||1033||1024||≈ 2047.999999999999772626||≈ 2.27374e-13|
|11||1034||2048||≈ 4095.999999999999545253||≈ 4.54747e-13|
|1023||2046||≈ 8.98847e307||≈ 1.79769e308||≈ 1.99584e292|
The standard also recommends extended format(s) to be used to perform internal computations at a higher precision than that required for the final result, to minimise round-off errors: the standard only specifies minimum precision and exponent requirements for such formats. The x87 80-bit extended format is the most commonly implemented extended format that meets these requirements.
Here are some examples of single-precision IEEE 754 representations:
|Type||Sign||Actual Exponent||Exp (biased)||Exponent field||Fraction field||Value|
|Zero||0||−126||0||0000 0000||000 0000 0000 0000 0000 0000||0.0|
|Negative zero||1||−126||0||0000 0000||000 0000 0000 0000 0000 0000||−0.0|
|One||0||0||127||0111 1111||000 0000 0000 0000 0000 0000||1.0|
|Minus One||1||0||127||0111 1111||000 0000 0000 0000 0000 0000||−1.0|
|Smallest denormalized number||*||−126||0||0000 0000||000 0000 0000 0000 0000 0001||±2−23 × 2−126 = ±2−149 ≈ ±1.4×10−45|
|"Middle" denormalized number||*||−126||0||0000 0000||100 0000 0000 0000 0000 0000||±2−1 × 2−126 = ±2−127 ≈ ±5.88×10−39|
|Largest denormalized number||*||−126||0||0000 0000||111 1111 1111 1111 1111 1111||±(1−2−23) × 2−126 ≈ ±1.18×10−38|
|Smallest normalized number||*||−126||1||0000 0001||000 0000 0000 0000 0000 0000||±2−126 ≈ ±1.18×10−38|
|Largest normalized number||*||127||254||1111 1110||111 1111 1111 1111 1111 1111||±(2−2−23) × 2127 ≈ ±3.4×1038|
|Positive infinity||0||128||255||1111 1111||000 0000 0000 0000 0000 0000||+∞|
|Negative infinity||1||128||255||1111 1111||000 0000 0000 0000 0000 0000||−∞|
|Not a number||*||128||255||1111 1111||non zero||NaN|
|* Sign bit can be either 0 or 1 .|
Comparing floating-point numbersEdit
Every possible bit combination is either a NaN or a number with a unique value in the affinely extended real number system with its associated order, except for the two bit combinations negative zero and positive zero, which sometimes require special attention (see below). The binary representation has the special property that, excluding NaNs, any two numbers can be compared as sign and magnitude integers (endianness issues apply). When comparing as 2's-complement integers: If the sign bits differ, the negative number precedes the positive number, so 2's complement gives the correct result (except that negative zero and positive zero should be considered equal). If both values are positive, the 2's complement comparison again gives the correct result. Otherwise (two negative numbers), the correct FP ordering is the opposite of the 2's complement ordering.
Rounding errors inherent to floating point calculations may limit the use of comparisons for checking the exact equality of results. Choosing an acceptable range is a complex topic.
Although negative zero and positive zero are generally considered equal for comparison purposes, some programming language relational operators and similar constructs treat them as distinct. According to the Java Language Specification, comparison and equality operators treat them as equal, but
Math.max() distinguish them (officially starting with Java version 1.1 but actually with 1.1.1), as do the comparison methods
compareTo() and even
compare() of classes
Rounding floating-point numbersEdit
The IEEE standard has four different rounding modes; the first is the default; the others are called directed roundings.
- Round to Nearest – rounds to the nearest value; if the number falls midway it is rounded to the nearest value with an even (zero) least significant bit, which means it is rounded up 50% of the time (in IEEE 754-2008 this mode is called roundTiesToEven to distinguish it from another round-to-nearest mode)
- Round toward 0 – directed rounding towards zero
- Round toward +∞ – directed rounding towards positive infinity
- Round toward −∞ – directed rounding towards negative infinity.
Extending the real numbersEdit
The IEEE standard employs (and extends) the affinely extended real number system, with separate positive and negative infinities. During drafting, there was a proposal for the standard to incorporate the projectively extended real number system, with a single unsigned infinity, by providing programmers with a mode selection option. In the interest of reducing the complexity of the final standard, the projective mode was dropped, however. The Intel 8087 and Intel 80287 floating point co-processors both support this projective mode.
Functions and predicatesEdit
The following functions must be provided:
- Add, subtract, multiply, divide
- Square root
- Floating point remainder. This is not like a normal modulo operation, it can be negative for two positive numbers. It returns the exact value of x–(round(x/y)·y).
- Round to nearest integer. For undirected rounding when halfway between two integers the even integer is chosen.
- Comparison operations. Besides the more obvious results, IEEE 754 defines that −∞ = −∞, +∞ = +∞ and x ≠
NaNfor any x (including
Recommended functions and predicatesEdit
copysign(x,y)returns x with the sign of y, so
copysign(x,1.0). This is one of the few operations which operates on a NaN in a way resembling arithmetic. The function
copysignis new in the C99 standard.
- −x returns x with the sign reversed. This is different from 0−x in some cases, notably when x is 0. So −(0) is −0, but the sign of 0−0 depends on the rounding mode.
finite(x)a predicate for "x is a finite value", equivalent to −Inf < x < Inf
isnan(x)a predicate for "x is a NaN", equivalent to "x ≠ x"
x <> ywhich turns out to have different exception behavior than NOT(x = y).
unordered(x, y)is true when "x is unordered with y", i.e., either x or y is a NaN.
nextafter(x,y)returns the next representable value from x in the direction towards y
In 1976 Intel began planning to produce a floating point coprocessor. John Palmer, the manager of the effort, persuaded them that they should try to develop a standard for all their floating point operations. William Kahan was hired as a consultant; he had helped improve the accuracy of Hewlett-Packard's calculators. Kahan initially recommended that the floating point base be decimal but the hardware design of the coprocessor was too far along to make that change.
The work within Intel worried other vendors, who set up a standardization effort to ensure a 'level playing field'. Kahan attended the second IEEE 754 standards working group meeting, held in November 1977. Here, he received permission from Intel to put forward a draft proposal based on the standard arithmetic part of their design for a coprocessor. The arguments over gradual underflow lasted until 1981 when an expert hired by DEC to assess it sided against the dissenters.
Even before it was approved, the draft standard had been implemented by a number of manufacturers. The Intel 8087, which was announced in 1980, was the first chip to implement the draft standard.
- Precision: The number of decimal digits precision is calculated via number_of_mantissa_bits * Log10(2). Thus ~7.2 and ~15.9 for single and double precision respectively.
- IEEE Standard for Binary Floating-Point Arithmetic. 1985. doi:10.1109/IEEESTD.1985.82928.
- Hennessy. Computer Organization and Design. Morgan Kaufmann. p. 270.
- Hossam A. H. Fahmy; Shlomo Waser; Michael J. Flynn, Computer Arithmetic (PDF), archived from the original (PDF) on 2010-10-08, retrieved 2011-01-02
- William Kahan. "Lecture Notes on the Status of IEEE 754" (PDF). October 1, 1997 3:36 am. Elect. Eng. & Computer Science University of California. Retrieved 2007-04-12.
- "Java Language and Virtual Machine Specifications". Java Documentation.
- John R. Hauser (March 1996). "Handling Floating-Point Exceptions in Numeric Programs" (PDF). ACM Transactions on Programming Languages and Systems. 18 (2): 139–174. doi:10.1145/227699.227701.
- David Stevenson (March 1981). "IEEE Task P754: A proposed standard for binary floating-point arithmetic". IEEE Computer. 14 (3): 51–62. doi:10.1109/C-M.1981.220377.
- William Kahan and John Palmer (1979). "On a proposed floating-point standard". SIGNUM Newsletter. 14 (Special): 13–21. doi:10.1145/1057520.1057522.
- W. Kahan 2003, pers. comm. to Mike Cowlishaw and others after an IEEE 754 meeting[unreliable source?]
- Charles Severance (20 February 1998). "An Interview with the Old Man of Floating-Point".
- Charles Severance. "History of IEEE Floating-Point Format". Connexions.
- Charles Severance (March 1998). "IEEE 754: An Interview with William Kahan" (PDF). IEEE Computer. 31 (3): 114–115. doi:10.1109/MC.1998.660194. Retrieved 2008-04-28.
- David Goldberg (March 1991). "What Every Computer Scientist Should Know About Floating-Point Arithmetic" (PDF). ACM Computing Surveys. 23 (1): 5–48. doi:10.1145/103162.103163. Retrieved 2008-04-28.
- Chris Hecker (February 1996). "Let's Get To The (Floating) Point" (PDF). Game Developer Magazine: 19–24. ISSN 1073-922X.
- David Monniaux (May 2008). "The pitfalls of verifying floating-point computations". ACM Transactions on Programming Languages and Systems. 30 (3): 1–41. arXiv:cs/0701192. doi:10.1145/1353445.1353446. ISSN 0164-0925.: A compendium of non-intuitive behaviours of floating-point on popular architectures, with implications for program verification and testing.