Excerpt from http://www.sourceware.org/ml/libc-alpha/2013-09/msg00664.html --- However, since there are two separate but related problems (AS-safe access to TLS variables, and ensuring allocation failure is reliably indicated by pthread_create or dlopen failure, rather than happening on access to a TLS variable when there is no good way to return a failure status), considering how the design for fixing one problem relates to the other problem (e.g. whether it introduces new code that would need to be removed again when fixing the other problem) is certainly relevant. --- The AS-safe part is PR16133