[Bug c/54129] New: __thread variables and pthread_*specific data destroyed in different order on Darwin than Linux

2012-07-30 Thread blucia at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54129 Bug #: 54129 Summary: __thread variables and pthread_*specific data destroyed in different order on Darwin than Linux Classification: Unclassified Product: gcc Version: 4.7.0

[Bug middle-end/54129] emulated __thread variables and pthread_*specific data

2012-07-30 Thread blucia at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54129 --- Comment #2 from blucia at gmail dot com 2012-07-30 20:25:52 UTC --- The man page for pthread_key_create says: An optional destructor function may be associated with each key value. ... The order of destructor calls is unspecified if more

[Bug middle-end/54129] emulated __thread variables and pthread_*specific data

2012-07-30 Thread blucia at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54129 --- Comment #4 from blucia at gmail dot com 2012-07-30 20:40:31 UTC --- I don't really see your point. Where is the code in the destructor for the __thread variables? For the pthread_key_create vars, I wrote down what I want to do to the data

[Bug middle-end/54129] emulated __thread variables and pthread_*specific data

2012-07-30 Thread blucia at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54129 --- Comment #6 from blucia at gmail dot com 2012-07-30 21:00:56 UTC --- Thanks for pointing out where that code is. I still think this is weird (i.e., possibly a bug) for two reasons: 1)Differs from Linux behavior. I'm sure lots of things