Re: pthread library related

[Charles Cui <charles.cui1984%gmail.com@localhost>]

Yes, I can do 2 and 5,  and fix 3.
I am now in the progress of porting ad's patch, let's complete it.
Once I have verified the porting part is done (compile new kernel , run
benchmarks, see errors does not exist),
I will return to complete 2, 5 and fix 3, sounds good?
Of course, I will send you guys the patch of the porting work shortly.


2016-05-26 15:02 GMT-07:00 Christos Zoulas <christos%zoulas.com@localhost>:

> On May 26,  2:08pm, charles.cui1984%gmail.com@localhost (Charles Cui) wrote:
> -- Subject: Re: pthread library related
>
> 1. SIGRTMIN/SIGRTMAX should not be exposed (the kernel does not support
>    the functionality).
> 2. I guess the bsd_signal is ok, but I don't like it :-)
>
> http://pubs.opengroup.org/onlinepubs/009695399/functions/bsd_signal.html
> 3. The pthread_condattr_getclock() prototype is wrong:
>
> http://pubs.opengroup.org/onlinepubs/009695399/functions/pthread_condattr_getclock.html
> 4. pthread_barrierattr_{get,set}pshared. I am ambivalent about that one
> because
>    I am afraid programs might discover it and think erroneously that we
> support
>    it. Let's wait on that.
> 5. _SC_SEM_NSEMS_MAX, although that's not the real limit, good enough.
>
> So let's not do 1, lets do 2, 5, fix 3 and wait for 4 until we understand
> it better.
>
> christos
>