Re: [PATCH] Introduce gsync-based locks to glibc.

2016-10-17 Thread Samuel Thibault
Hello, Agustina Arzille, on Mon 23 May 2016 19:43:52 -0300, wrote: > Here's the updated glibc patch, and the patches for mutexes and rwlocks. I have had a look, there are licence/copyright issues: - the new files you created are under GPLv3+, that's no good for libpthread, which we need to use

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-08-23 Thread Samuel Thibault
Samuel Thibault, on Tue 23 Aug 2016 22:34:41 +0200, wrote: > and uploaded a package to debian, That'll be libc0.3 2.23-5, will probably be available about tomorrow. Samuel

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-08-23 Thread Samuel Thibault
Hello, I have cleaned the patch a bit, commited to a branch in our repo, and uploaded a package to debian, so we can test the libc part for now, and we'll include libpthread parts later. Thanks again for the great work! Samuel

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-08-22 Thread Samuel Thibault
Samuel Thibault, on Sun 21 Aug 2016 02:32:58 +0200, wrote: > Samuel Thibault, on Sat 20 Aug 2016 22:41:37 +0200, wrote: > > The good news is that there are only half a dozen test regressions. > > The even more good news is that these are most probably actually due to > a bogus DNS resolution confi

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-08-20 Thread Samuel Thibault
Samuel Thibault, on Sat 20 Aug 2016 22:41:37 +0200, wrote: > The good news is that there are only half a dozen test regressions. The even more good news is that these are most probably actually due to a bogus DNS resolution configuration on my system :) Samuel

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-08-20 Thread Samuel Thibault
Hello, Agustina Arzille, on Fri 20 May 2016 00:43:37 -0300, wrote: > Here are the patches needed to get the ball rolling and finally introduce > gsync-based synchronization objects into our libc. Thanks to the coach back home, I got the time to have a look at integrating this. The good news is t

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-05-23 Thread Agustina Arzille
Here's the updated glibc patch, and the patches for mutexes and rwlocks. The initial patch for libpthread as published in: http://lists.gnu.org/archive/html/bug-hurd/2016-05/msg00027.html remains the same. * hurd/hurdlock.h: New file. * hurd/hurdlock.c: New file. * hurd/Makefile: Add hurdlock

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-05-23 Thread Agustina Arzille
On 05/22/2016 03:47 AM, Kalle Olavi Niemitalo wrote: GPLv3-based licenses may be OK for tests (libio/tst-fwrite-error.c) but I think not for code that gets loaded from glibc to application processes, unless a license exception applies (intl/plural.c). There seems to be a similar problem with in

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-05-21 Thread Kalle Olavi Niemitalo
Agustina Arzille writes: > +++ b/hurd/hurdlock.c > +++ b/hurd/hurdlock.h > +++ b/mach/lowlevellock.h Those new files still have LGPLv3-or-later notices in them: > + The GNU C Library is free software; you can redistribute it and/or > + modify it under the terms of the GNU Lesser General Pub

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-05-20 Thread Agustina Arzille
Hello, Samuel, On 05/20/2016 04:15 AM, Samuel Thibault wrote: Just a nitpick (but important one since otherwise I'd have to do the work myself): we need a ChangeLog in the GNU style, i.e. not only the rationale as you wrote (which is very useful!) but also a description of the changes themselves

Re: [PATCH] Introduce gsync-based locks to glibc.

2016-05-20 Thread Samuel Thibault
Hello, Agustina Arzille, on Fri 20 May 2016 00:43:37 -0300, wrote: > Here's a list of changes: Just a nitpick (but important one since otherwise I'd have to do the work myself): we need a ChangeLog in the GNU style, i.e. not only the rationale as you wrote (which is very useful!) but also a descr

[PATCH] Introduce gsync-based locks to glibc.

2016-05-19 Thread Agustina Arzille
Hello, everyone. Here are the patches needed to get the ball rolling and finally introduce gsync-based synchronization objects into our libc. These 2 first patches modify the internal locks used by glibc and some bits in libpthread that will be necessary for more complex objects. There are quite