summaryrefslogtreecommitdiff
path: root/open_issues/glibc/t
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2013-10-27 19:15:06 +0100
committerThomas Schwinge <tschwinge@gnu.org>2013-10-27 19:15:06 +0100
commit47e4d194dc36adfcfd2577fa4630c9fcded005d3 (patch)
treed16ffd2eeb74d1977fb3e9744e4a38befedb4ddf /open_issues/glibc/t
parentca39ad0592e9b99dac9d99c68bb36ef1d27f72df (diff)
IRC.
Diffstat (limited to 'open_issues/glibc/t')
-rw-r--r--open_issues/glibc/t/tls-threadvar.mdwn37
1 files changed, 37 insertions, 0 deletions
diff --git a/open_issues/glibc/t/tls-threadvar.mdwn b/open_issues/glibc/t/tls-threadvar.mdwn
index 7ce36f41..40d1463e 100644
--- a/open_issues/glibc/t/tls-threadvar.mdwn
+++ b/open_issues/glibc/t/tls-threadvar.mdwn
@@ -116,3 +116,40 @@ dropped altogether, and `__thread` directly be used in glibc.
## IRC, OFTC, #debian-hurd, 2013-09-23
<youpi> yay, errno threadvar conversion success
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-05
+
+ <gg0_> youpi: any ETA for tls?
+ <youpi> gg0_: one can't have an ETA for bugfixing
+ <gg0_> i don't call them bugs if there's something missing to implement btw
+ <youpi> no, here it's bugs
+ <youpi> the implementation is already in the glibc branches in our
+ repository
+ <youpi> it just makes some important regressions
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-07
+
+ <youpi> about tls, I've made some "progress": now I'm wondering how raise()
+ has ever been working before :)
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-15
+
+ <youpi> good, reply_port tls is now ok
+ <youpi> last but not least, sigstate
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-21
+
+ <youpi> started testsuite with threadvars dropped completely
+ <youpi> so far so good
+
+
+## IRC, OFTC, #debian-hurd, 2013-10-24
+
+ <youpi> ok, hurd boots with full-tls libc, no threadvars at all any more
+ <gg0> \o/
+ <gg0> good bye threadvars bugs, welcome tls ones ;)
+ <youpi> now I need to check that threads can really use another stack :)