{"push_id":1433607450,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"48869ad3cbf6fc27b708d4e4b0eef66f9049f6e8","before":"92befdd754a23ebb3b0428bf78713980663fca6f","commits":[{"sha":"48869ad3cbf6fc27b708d4e4b0eef66f9049f6e8","author":{"name":"Derek Bruening","email":"5c9304747aa76bca89fdf247a67e2d731beb81a9@google.com"},"message":"i#2089 TLS init: add a safe read path for is_thread_tls_initialized()\n\nThis is a first step toward solving several issues with\nis_thread_tls_initialized() by switching to using a new\nsafe_read_tls_base() step.  A new assembly routine and fault handling path\nare added, along with globals to avoid the complexity of attempting this\nduring process init or exit.\n\nThis also fixes the TLS issues with the Windows Subsystem for Linux\n(i#1986) and with other cases where it is very difficult to determine\nwhether TLS is initialized or not: it is much simpler to simply attempt to\nread it.\n\nThe new code is under an off-by-default option -safe_read_tls_init until\nwe have the other pieces of the new TLS scheme in place.  Without the\nforthcoming pieces, we incur a fault on every new thread init and exit.\n\nReview-URL: https://codereview.appspot.com/313150043","distinct":true,"url":"https://api.github.com/repos/DynamoRIO/dynamorio/commits/48869ad3cbf6fc27b708d4e4b0eef66f9049f6e8"}]}
{"actor":{"display_login":"derekbruening"}}