aboutsummaryrefslogtreecommitdiff
path: root/open_issues/glibc/t
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/glibc/t')
-rw-r--r--open_issues/glibc/t/tls-threadvar.mdwn37
-rw-r--r--open_issues/glibc/t/tls.mdwn9
2 files changed, 46 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 :)
diff --git a/open_issues/glibc/t/tls.mdwn b/open_issues/glibc/t/tls.mdwn
index a92a21fb..b10703fd 100644
--- a/open_issues/glibc/t/tls.mdwn
+++ b/open_issues/glibc/t/tls.mdwn
@@ -70,3 +70,12 @@ After commit a9538892adfbb9f092e0bb14ff3a1703973968af, it's
much better.
<youpi> have you had a look at the tls.pdf from Uli ?
<youpi> all the gory details are there :)
+
+Commit c61b4d41c9647a54a329aa021341c0eb032b793e, [[!sourceware_PR 15754]], adds
+`sysdeps/i386/stackguard-macros.h:POINTER_CHK_GUARD`, which is not correct for
+us (at the moment), but it also shouldn't cause any harm, as this file is only
+used in `elf/tst-ptrguard1.c` and `elf/tst-stackguard1.c`, which now will fail
+to build for us, as we don't have a `pointer_guard` member in
+`sysdeps/mach/hurd/tls.h:tcbhead_t`.
+
+We don't define `THREAD_SET_POINTER_GUARD`.