From 2603401fa1f899a8ff60ec6a134d5bd511073a9d Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 7 Aug 2012 23:25:26 +0200 Subject: IRC. --- open_issues/glibc/t/tls-threadvar.mdwn | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) (limited to 'open_issues/glibc') diff --git a/open_issues/glibc/t/tls-threadvar.mdwn b/open_issues/glibc/t/tls-threadvar.mdwn index e72732ab..4afd8a1a 100644 --- a/open_issues/glibc/t/tls-threadvar.mdwn +++ b/open_issues/glibc/t/tls-threadvar.mdwn @@ -29,3 +29,32 @@ IRC, freenode, #hurd, 2011-10-23: After this has been done, probably the whole `__libc_tsd_*` stuff can be dropped altogether, and `__thread` directly be used in glibc. + + +# IRC, freenode, #hurd, 2012-08-07 + + r5219: Update libpthread patch to replace threadvar with tls + for pthread_self + r5224: revert r5219 too, it's not ready either + as the changelog says, the __thread revertal is because it posed + problems + and I just didn't have any time to check them while the freeze was + so close + OK. What kind of problems? Should it be reverted upstream, + too? + I don't remember exactly + it should just be fixed + we can revert it upstream, but it'd be good that we manage to + progress, at some point... + Of course -- however as long as we don't know what kind of + problem, it is a bit difficult. ;-) + since I didn't left a note, it was most probably a mere glibc run, + or boot with the patched libpthread + *testsuite run + OK. + The libpthread testsuite doesn't show any issues with that + patch applied, though. But I didn'T test anything else. + youpi: Also, you have probably seen my glibc __thread errno + email -- rmcgrath wanted to find some time this week to comment/help, and + I take it you don't have any immediate comments to that issue? + I saw the mails, but didn't investigate at all -- cgit v1.2.3