Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

75%
+4 −0
Q&A Static and thread_local initialization order

Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program? #include<iostream> s...

1 answer  ·  posted 4y ago by Estela‭  ·  edited 4y ago by Alexei‭

#3: Post edited by user avatar Alexei‭ · 2020-11-19T20:07:23Z (about 4 years ago)
added relevant tags
  • Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program?
  • #include<iostream>
  • static int a=3;
  • thread_local int b=a;
  • int main(void) {
  • std::cout << b << std::endl;
  • }
  • For threads other than the 1st one surely thread_local objects will be initialized after statics(*). But does the C++ standard provide any guarantee that thread_local objects will be initialized after static objects for the 1st thread?
  • (*) Unless the thread is started from the constructor of a global/static object. But not going there.
  • Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program?
  • #include<iostream>
  • static int a=3;
  • []() int b=a;
  • int main(void) {
  • std::cout << b << std::endl;
  • }
  • For threads other than the 1st one surely thread_local objects will be initialized after statics(*). But does the C++ standard provide any guarantee that thread_local objects will be initialized after static objects for the 1st thread?
  • (*) Unless the thread is started from the constructor of a global/static object. But not going there.
#2: Post edited by user avatar Estela‭ · 2020-11-17T09:45:46Z (about 4 years ago)
  • Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program?
  • #include<iostream>
  • static int a=3;
  • thread_local int b=a;
  • int main(void) {
  • std::cout << b << std::endl;
  • }
  • For threads other than the 1st one surely thread_local objects will be initialized after statics(*). But does the C++ standard provide any guarantee that thread_local objects will be initialized after static objects for the 1st thread?
  • (*) Unless the thread is started from the constructor of an static object. But not going there.
  • Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program?
  • #include<iostream>
  • static int a=3;
  • thread_local int b=a;
  • int main(void) {
  • std::cout << b << std::endl;
  • }
  • For threads other than the 1st one surely thread_local objects will be initialized after statics(*). But does the C++ standard provide any guarantee that thread_local objects will be initialized after static objects for the 1st thread?
  • (*) Unless the thread is started from the constructor of a global/static object. But not going there.
#1: Initial revision by user avatar Estela‭ · 2020-11-17T07:02:47Z (about 4 years ago)
Static and thread_local initialization order
Is there any guarantee regarding initialization of static and thread_local objects? In example, is there any guarantee about the value printed by the following program?

    #include<iostream>
    static int a=3;
    thread_local int b=a;
    int main(void) {
        std::cout << b << std::endl;
    }

For threads other than the 1st one surely thread_local objects will be initialized after statics(*). But does the C++ standard provide any guarantee that thread_local objects will be initialized after static objects for the 1st thread?

(*) Unless the thread is started from the constructor of an static object. But not going there.
c++