Re: hppa nptl switch
On Wed, Aug 19, 2009 at 8:48 AM, Aurelien Jarno<firstname.lastname@example.org> wrote:
> [Changing debian-bsd to debian-glibc, probably more appropriate to
> discuss about the internal glibc code ;-)]
>> > may I ask you for status of hppa nptl switch ?
I spent the last two days rewriting the pthread structure layouts for
hppa's nptl implementation.
Thanks to Petr's insight, I was able to restructure both
pthread_mutex_t, and pthread_rwlock_t to be 100% ABI compatible with
In the case of pthread_cond_t, the structure grew so much, that I had
to use some of the old lock words (non-zero initialized words) for new
fields, and this meant that all of the pthread_cond_* functions will
quickly test and zero pthread_cond_t before use. The new NPTL
PTHREAD_COND_INITIALIZER uses the fast-path in the code, thus as
applications are rebuilt they will run faster.
The prototype patch in testing is here:
This patch is not the final version, I need to remove the
old_pthread_cond_* functions, and cleanup the pthread_cond_* functions
to use the same version number. At the end of the day I'm not going to
version any of the functions, because technically they will be ABI
compatible. I will however, surround the checking code with some
version checks so it can be removed in the future (or generate a
Please note that the new code *will* support partial upgrades for
debian, since this is a 100% ABI compatible change.
I will report back over the next few days on the status of testing the