What is the size of float and double in C and C++? [duplicate]

by

Excerpt from the C99 standard, normative annex F (The C++-standard does not explicitly mention this annex, though it includes all affected functions without change per reference. Also, the types have to match for compatibility.):

IEC 60559 floating-point arithmetic

F.1 Introduction

1 This annex specifies C language support for the IEC 60559 floating-point standard. The
IEC 60559 floating-point standard is specifically Binary floating-point arithmetic for
microprocessor systems, second edition (IEC 60559:1989), previously designated
IEC 559:1989 and as IEEE Standard for Binary Floating-Point Arithmetic
(ANSI/IEEE 754−1985). IEEE Standard for Radix-Independent Floating-Point
Arithmetic (ANSI/IEEE 854−1987) generalizes the binary standard to remove
dependencies on radix and word length. IEC 60559 generally refers to the floating-point
standard, as in IEC 60559 operation, IEC 60559 format, etc. An implementation that
defines __STDC_IEC_559__ shall conform to the specifications in this annex.356)
Where a binding between the C language and IEC 60559 is indicated, the
IEC 60559-specified behavior is adopted by reference, unless stated otherwise. Since
negative and positive infinity are representable in IEC 60559 formats, all real numbers lie
within the range of representable values.

So, include <math.h> (or in C++ maybe <cmath>), and test for __STDC_IEC_559__.

If the macro is defined, not only are the types better specified (float being 32bits and double being 64bits among others), but also the behavior of builtin operators and standard-functions is more specified.
Lack of the macro does not give any guarantees.

For x86 and x86_64 (amd64), you can rely on the types float and double being IEC-60559-conformant, though functions using them and operations on them might not be.

More Related Contents:

  1. Floating point vs integer calculations on modern hardware
  2. Difference in floating point arithmetics between x86 and x64
  3. Change floating point rounding mode
  4. How do I print a double value with full precision using cout?
  5. Why does C++ code for testing the Collatz conjecture run faster than hand-written assembly?
  6. Can modern x86 hardware not store a single byte to memory?
  7. Replacing a 32-bit loop counter with 64-bit introduces crazy performance deviations with _mm_popcnt_u64 on Intel CPUs
  8. Deoptimizing a program for the pipeline in Intel Sandybridge-family CPUs
  9. Sin and Cos give unexpected results for well-known angles
  10. Why is my integer math with std::pow giving the wrong answer?
  11. Getting the high part of 64 bit integer multiplication
  12. Is there any “standard” htonl-like function for 64 bits integers in C++?
  13. Where is the lock for a std::atomic?
  14. Atomic operations, std::atomic and ordering of writes
  15. What happens when a computer program runs?
  16. How to generate assembly code with clang in Intel syntax?
  17. How computer does floating point arithmetic?
  18. How to correctly and standardly compare floats?
  19. Convert a float to a string
  20. Math precision requirements of C and C++ standard
  21. How large is a DWORD with 32- and 64-bit code?
  22. Does hardware memory barrier make visibility of atomic operations faster in addition to providing necessary guarantees?
  23. Why do sin(45) and cos(45) give different results? [duplicate]
  24. C++ floating point to integer type conversions
  25. Printing double without losing precision
  26. .net Framework Error (HRESULT 0x8007000B)
  27. When a float variable goes out of the float limits, what happens?
  28. How is floating point conversion actually done in C++?(double to float or float to double)
  29. How to force GCC to assume that a floating-point expression is non-negative?
  30. Is there any advantage to using pow(x,2) instead of x*x, with x double?

Leave a Comment