From 78d2510a84a791479ff0bad78e21aca6c4ce78fa Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 21 May 2013 14:27:40 +0200 Subject: open_issues/glibc: bab06390aca40703514099a7022dac4ae4aac76b (2013-05-20; fbeafedeea37e0af1984a6511018d159f5ceed6a (2012-11-03)) --- open_issues/glibc/t/tls-threadvar.mdwn | 56 ---------------------------------- 1 file changed, 56 deletions(-) (limited to 'open_issues/glibc') diff --git a/open_issues/glibc/t/tls-threadvar.mdwn b/open_issues/glibc/t/tls-threadvar.mdwn index 5f1345c6..105a07c7 100644 --- a/open_issues/glibc/t/tls-threadvar.mdwn +++ b/open_issues/glibc/t/tls-threadvar.mdwn @@ -64,59 +64,3 @@ dropped altogether, and `__thread` directly be used in glibc. I saw the mails, but didn't investigate at all [[!message-id "878vdyqht3.fsf@kepler.schwinge.homeip.net"]]. - - -# `getcontext`/`setcontext` - -Needed for [[gccgo]]. - -Instead of adding support for `getcontext`/`setcontext` within the Hurd -threadvar context, which might become a bit ugly, the idea is to get rid of -Hurd threadvars and replace them with TLS (as we want to, anyway). - - -## IRC, freenode, #hurd, 2012-04-19 - - How much work/knowledge is needed to implement - getcontext/setcontext? - Any already implemented alternatives available? - x86 registers knowledge, as well as unix signal masks - there's the linux implementation that can be taken as an - exxample, but the signal part has to be rewritten - Well, it's a pity they are not implemented. That's the - remaining hurdle to get gccgo working :-( - uh :/ - Everything builds, but the testsuite fails due to these - missing functions. - Regarding getcontext/setcontext they seem to be written - in assembly for linux but the code is not very long. - How much effort would it be to write something similar - for Hurd? Anybody fluent in asm? - And registers and signals. - gnu_srs: Signals is the key thing -- everything else we - can probably just copy. I have never/not yet looked at it, - though. - For kfreebsd it is written in C: kern_context.c, 3/4 in - one file: getcontext, setcontext, swapcontext, not makecontext. - Dunno how much assembly calls used though. - Hi, any preferences about implementing get/setcontext in - C or Asm? - gnu_srs: I think these will have to be implemented in - assembly. Based on the Linux x86 variants. - - -### IRC, freenode, #hurd, 2012-04-20 - - youpi: Your understanding of that is better than mine - -- the *context stuff can't be very useful at the moment, because - when the user changes uc_stack.ss_sp (which the glibc tests are - doing), we're losing access to the _hurd_threadvars. Correct? - At least the getcontext test works, the other get a - SIGILL. - others - _hurd_threadvars issue is just guessing. - tschwinge: yes, threadvars are on the stack - threadvars is not much code, it should just work, but care - has to be taken on the libpthread/libthread side, which does some - initialization - OK, that at least matches my understanding. -- cgit v1.2.3