Is global memory initialized in C++?

by

From the standard:

Objects with static storage duration (3.7.1) shall be zero-initialized (8.5) before any other initialization takes place. Zero-initialization and initialization with a constant expression are collectively called static initialization; all other initialization is dynamic initialization. Objects of POD [plain old data] types (3.9) with static storage duration initialized with constant expressions (5.19) shall be initialized before any dynamic initialization takes place. Objects with static storage duration defined in namespace scope in the same translation unit and dynamically initialized shall be initialized in the order in which their definition appears in the translation unit. [Note:8.5.1 describes the order in which aggregate members are initialized. The initial-
ization of local static objects is described in 6.7.]

So yes, globals which have static storage duration will be initialized. Globals allocated, e.g., on the heap will of course not be initialized automatically.

More Related Contents:

  1. Dynamic memory allocation in game server [closed]
  2. When and why will a compiler initialise memory to 0xCD, 0xDD, etc. on malloc/free/new/delete?
  3. General guidelines to avoid memory leaks in C++ [closed]
  4. Allocating more memory than there exists using malloc
  5. How do you determine the size of an object in C++?
  6. What is the behavior of “delete” with stack objects? [duplicate]
  7. What is “bit padding” or “padding bits” exactly?
  8. How do I call the original “operator new” if I have overloaded it?
  9. What does “Memory allocated at compile time” really mean?
  10. Class members and explicit stack/heap allocation
  11. Why is sizeof giving incorrect number of bytes in C++?
  12. How do malloc() and free() work?
  13. Is delete[] equal to delete?
  14. Which is faster: Stack allocation or Heap allocation
  15. Why aren’t pointers initialized with NULL by default?
  16. Compelling examples of custom C++ allocators?
  17. How to get available memory C++/g++?
  18. How does a C++ reference look, memory-wise?
  19. Any reason to overload global new and delete?
  20. Do class/struct members always get created in memory in the order they were declared?
  21. Are memory leaks “undefined behavior” class problem in C++?
  22. Check if a pointer points to allocated memory on the heap
  23. Reason why not to have a DELETE macro for C++
  24. g++ variable size array no warning?
  25. Why, really, deleting an incomplete type is undefined behaviour?
  26. How are String and Char types stored in memory in .NET?
  27. The difference between delete and delete[] in C++ [duplicate]
  28. Can you allocate a very large single chunk of memory ( > 4GB ) in c or c++?
  29. Can undefined behavior erase the hard drive?
  30. How to determine if returned pointer is on the stack or heap

Leave a Comment