Why do (only) some compilers use the same address for identical string literals?

by

This is not undefined behavior, but unspecified behavior. For string literals,

The compiler is allowed, but not required, to combine storage for equal or overlapping string literals. That means that identical string literals may or may not compare equal when compared by pointer.

That means the result of A == B might be true or false, on which you shouldn’t depend.

From the standard, [lex.string]/16:

Whether all string literals are distinct (that is, are stored in nonoverlapping objects) and whether successive evaluations of a string-literal yield the same or a different object is unspecified.

More Related Contents:

  1. Has C++ standard changed with respect to the use of indeterminate values and undefined behavior in C++14?
  2. Order of evaluation of arguments using std::cout
  3. Take the address of a one-past-the-end array element via subscript: legal by the C++ Standard or not?
  4. Do I need to cast to unsigned char before calling toupper(), tolower(), et al.?
  5. C++ multiline string literal
  6. Do distinct functions have distinct addresses?
  7. How can I get double quotes into a string literal?
  8. Why class data members can’t be initialized by direct initialization syntax?
  9. Is adding to a “char *” pointer UB, when it doesn’t actually point to a char array?
  10. Efficient unsigned-to-signed cast avoiding implementation-defined behavior
  11. Is a pointer with the right address and type still always a valid pointer since C++17?
  12. Floating point comparison revisited
  13. How to use Macro argument as string literal?
  14. Pure virtual functions may not have an inline definition. Why?
  15. What does the void() in decltype(void()) mean exactly?
  16. Are non dereferenced iterators past the “one past-the-end” iterator of an array undefined behavior?
  17. Can the point-of-instantiation be delayed until the end of the translation unit?
  18. Comparing character arrays and string literals in C++
  19. Is most vexing parse a formally defined concept
  20. Pseudo-destructor call does not destroy an object
  21. Why is a constexpr function on a reference not constexpr?
  22. Will consteval functions allow template parameters dependent on function arguments?
  23. Is the Empty Base Class Optimization now a mandatory optimization (at least for standard-layout classes)?
  24. Erasing vector::end from vector
  25. Classes with both template and non-template conversion operators in the condition of switch statement
  26. What is difference between const and non const key?
  27. Why does the template-id in “A=0” not compile without space because of the greater-or-equal-than operator “>=”?
  28. Injected class name compiler discrepancy
  29. What standard clause mandates this lvalue-to-rvalue conversion?
  30. Can SFINAE detect private access violations?

Leave a Comment