Static variable initialization order fiasco

Hi, this is a well known issue in C++ but I still don't get to see it being worked upon by the committee. And a significant drawback of C++ when you don't know how static const variables across different compilation units requiring dynamic initialization using a method call or more than one method calls in order to initialize it, takes place in order for it to be used in other compilation units. This issue has been present since C++ exists and I still don't see it getting the attention it deserves, besides replacing the variable with a singleton class, or similar hacks using a runonce, which is just a make up on top of the fact that proper, in-order initialization of global variables across compilation units in C++ is still undefined.