At Sat, 4 Aug 2012 12:34:28 +0200, Thomas Schwinge wrote: > There has been a libpthread port for Hurd on L4 use, which is dead, and > has been superseded by a Viengoos port, which has its own branches:
For what it is worth, the L4 port works directly on L4: no further OS personality support is required. On the other hand, no one actually uses it so I guess it is okay to remove it. > master-viengoos and its successor, master-viengoos-on-bare-metal. master-viengoos is an implementation of Viengoos that runs on L4. viengoos-on-bare-metal runs directly on x86-64 (and it a bit more advanced) and provides everything that master-viengoos does and more. I unfortunately never got around to issuing the right git commands to make turn it into the master branch. > * signal/README: Likewise. > * signal/TODO: Likewise. > * signal/kill.c: Likewise. > * signal/pt-kill-siginfo-np.c: Likewise. > * signal/sig-internal.c: Likewise. > * signal/sig-internal.h: Likewise. > * signal/sigaction.c: Likewise. > * signal/sigaltstack.c: Likewise. > * signal/signal-dispatch.c: Likewise. > * signal/signal.h: Likewise. > * signal/sigpending.c: Likewise. > * signal/sigsuspend.c: Likewise. > * signal/sigtimedwait.c: Likewise. > * signal/sigwaiter.c: Likewise. > * signal/sigwaitinfo.c: Likewise. > * sysdeps/generic/killpg.c: Likewise. > * sysdeps/generic/raise.c: Likewise. > * sysdeps/generic/sigaddset.c: Likewise. > * sysdeps/generic/sigdelset.c: Likewise. > * sysdeps/generic/sigemptyset.c: Likewise. > * sysdeps/generic/sigfillset.c: Likewise. > * sysdeps/generic/siginterrupt.c: Likewise. > * sysdeps/generic/sigismember.c: Likewise. > * sysdeps/generic/signal.c: Likewise. > * sysdeps/generic/sigwait.c: Likewise. I think these are also used by the Viengoos port. Are you suggesting to remove both the L4 and the Viengoos ports or just the L4 port? > Also, I propose to remove the incomplete and unmaintained PowerPC port. > OK? I have no objections to this. > In August 2008, Neal has been porting over some generic changes from the > Viengoos branch to master, and I'm now identifying if there are > additional changes to be ported. That's a good idea. Unfortunately, I don't remember how far I got. Note: libpthread is not without its problems, e.g., lack of testing in the wild. I still think the better way forward is to use Glibc's pthread, if possible. Neal
