Is floating point addition commutative in C++?

by

It is not even required that a + b == a + b. One of the subexpressions may hold the result of the addition with more precision than the other one, for example when the use of multiple additions requires one of the subexpressions to be temporarily stored in memory, when the other subexpression can be kept in a register (with higher precision).

If a + b == a + b is not guaranteed, a + b == b + a cannot be guaranteed. If a + b does not have to return the same value each time, and the values are different, one of them necessarily will not be equal to one particular evaluation of b + a.

More Related Contents:

  1. Floating point comparison revisited
  2. The behaviour of floating point division by zero
  3. reinterpret_cast creating a trivially default-constructible object
  4. Is it a conforming compiler extension to treat non-constexpr standard library functions as constexpr?
  5. Sin and Cos give unexpected results for well-known angles
  6. When using C headers in C++, should we use functions from std:: or the global namespace?
  7. Template partial ordering – why does partial deduction succeed here
  8. Matching alias template as template argument
  9. Unsequenced value computations (a.k.a sequence points)
  10. Why does same_as concept check type equality twice?
  11. Do all pointers have the same size in C++?
  12. Force all classes to implement / override a ‘pure virtual’ method in multi-level inheritance hierarchy
  13. Can class template constructors have a redundant template parameter list in c++20
  14. Is std::abs(0u) ill-formed?
  15. Why does the standard differentiate between direct-list-initialization and copy-list-initialization?
  16. Can std::launder be used to convert an object pointer to its enclosing array pointer?
  17. Does accessing the first field of a struct via a C cast violate strict aliasing?
  18. C++ – Why static member function can’t be created with ‘const’ qualifier
  19. Is a constexpr array necessarily odr-used when subscripted?
  20. Math precision requirements of C and C++ standard
  21. C++ floating point to integer type conversions
  22. When a float variable goes out of the float limits, what happens?
  23. Dangling references and undefined behavior
  24. Extra leading zeros when printing float using printf?
  25. Is there some meaningful statistical data to justify keeping signed integer arithmetic overflow undefined?
  26. Is it a strict aliasing violation to alias a struct as its first member?
  27. Does setprecision in c++ round? If so why am I seeing this?
  28. What is the modern, correct way to do type punning in C++?
  29. Overload resolution with ref-qualifiers
  30. Does the standard mandate an lvalue-to-rvalue conversion of the pointer variable when applying indirection?

Leave a Comment