Why are global and static variables initialized to their default values?

by

  1. Security: leaving memory alone would leak information from other processes or the kernel.

  2. Efficiency: the values are useless until initialized to something, and it’s more efficient to zero them in a block with unrolled loops. The OS can even zero freelist pages when the system is otherwise idle, rather than when some client or user is waiting for the program to start.

  3. Reproducibility: leaving the values alone would make program behavior non-repeatable, making bugs really hard to find.

  4. Elegance: it’s cleaner if programs can start from 0 without having to clutter the code with default initializers.

One might then wonder why the auto storage class does start as garbage. The answer is two-fold:

  1. It doesn’t, in a sense. The very first stack frame page at each level (i.e., every new page added to the stack) does receive zero values. The “garbage”, or “uninitialized” values that subsequent function instances at the same stack level see are really the previous values left by other method instances of your own program and its library.

  2. There might be a quadratic (or whatever) runtime performance penalty associated with initializing auto (function locals) to anything. A function might not use any or all of a large array, say, on any given call, and it could be invoked thousands or millions of times. The initialization of statics and globals, OTOH, only needs to happen once.

More Related Contents:

  1. When are static and global variables initialized?
  2. static and extern global variables in C and C++
  3. C++ singleton vs. global static object
  4. How to execute a piece of code only once?
  5. The static keyword and its various uses in C++
  6. Why does a static data member need to be defined outside of the class?
  7. Why can’t I initialize non-const static member or static array in class?
  8. Defining static const integer members in class definition
  9. Static member initialization in a class template
  10. static constructors in C++? I need to initialize private static objects
  11. Static variables in member functions
  12. conversion of 2D array to pointer-to-pointer
  13. Static variables in C++
  14. Does C++ call destructors for global and class static variables?
  15. Does there exist a static_warning?
  16. Are function static variables thread-safe in GCC?
  17. C++ where to initialize static const
  18. Template static variable
  19. Variable declarations in header files – static or not?
  20. C++: When (and how) are C++ Global Static Constructors Called?
  21. What makes a static variable initialize only once?
  22. Circular C++ Header Includes
  23. static vs non-static variables in namespace
  24. How do static variables in lambda function objects work?
  25. Advantages of classes with only static methods in C++
  26. Is C++ static member variable initialization thread-safe?
  27. When and why would you use static with constexpr?
  28. how to declare and define global variables in order to access them from all headers/source files properly
  29. How to ignore false positive memory leaks from _CrtDumpMemoryLeaks?
  30. What are the pros and cons in use of global variables? [closed]

Leave a Comment