What range of numbers can be represented in a 16-, 32- and 64-bit IEEE-754 systems?

by

For a given IEEE-754 floating point number X, if

2^E <= abs(X) < 2^(E+1)

then the distance from X to the next largest representable floating point number (epsilon) is:

epsilon = 2^(E-52)    % For a 64-bit float (double precision)
epsilon = 2^(E-23)    % For a 32-bit float (single precision)
epsilon = 2^(E-10)    % For a 16-bit float (half precision)

The above equations allow us to compute the following:

  • For half precision…

    If you want an accuracy of +/-0.5 (or 2^-1), the maximum size that the number can be is 2^10. Any larger than this and the distance between floating point numbers is greater than 0.5.

    If you want an accuracy of +/-0.0005 (about 2^-11), the maximum size that the number can be is 1. Any larger than this and the distance between floating point numbers is greater than 0.0005.

  • For single precision…

    If you want an accuracy of +/-0.5 (or 2^-1), the maximum size that the number can be is 2^23. Any larger than this and the distance between floating point numbers is greater than 0.5.

    If you want an accuracy of +/-0.0005 (about 2^-11), the maximum size that the number can be is 2^13. Any larger than this and the distance between floating point numbers is greater than 0.0005.

  • For double precision…

    If you want an accuracy of +/-0.5 (or 2^-1), the maximum size that the number can be is 2^52. Any larger than this and the distance between floating point numbers is greater than 0.5.

    If you want an accuracy of +/-0.0005 (about 2^-11), the maximum size that the number can be is 2^42. Any larger than this and the distance between floating point numbers is greater than 0.0005.

More Related Contents:

  1. Next higher/lower IEEE double precision number
  2. Why are floating point numbers inaccurate?
  3. What is the rationale for all comparisons returning false for IEEE754 NaN values?
  4. Why do I see a double variable initialized to some value like 21.4 as 21.399999618530273?
  5. What is the difference between float and double?
  6. Is floating-point math consistent in C#? Can it be?
  7. Why is NaN not equal to NaN? [duplicate]
  8. What is the difference between quiet NaN and signaling NaN?
  9. Why converting from float to double changes the value?
  10. Representing integers in doubles
  11. Why does IEEE 754 reserve so many NaN values?
  12. Extreme numerical values in floating-point precision in R
  13. Matlab vs C++ Double Precision
  14. Why IEEE754 single-precision float has only 7 digit precision?
  15. How to perform round to even with floating point numbers
  16. What uses do floating point NaN payloads have?
  17. Maximum number of decimal digits that can affect a double
  18. Why does >= operator work as > operator in C when compared with 0.9 [duplicate]
  19. Which is the first integer that an IEEE 754 float is incapable of representing exactly?
  20. Limiting floats to two decimal points
  21. How to calculate float type precision and does it make sense?
  22. In which order should floats be added to get the most precise result?
  23. python floating number [duplicate]
  24. Floating Point Limitations [duplicate]
  25. Does JavaScript have double floating point number precision?
  26. Is it safe to assume floating point is represented using IEEE754 floats in C?
  27. Why does the floating-point value of 4*0.1 look nice in Python 3 but 3*0.1 doesn’t?
  28. What’s the relative speed of floating point add vs. floating point multiply
  29. Can I use the AVX FMA units to do bit-exact 52 bit integer multiplications?
  30. Golang converting float64 to int error

Leave a Comment