Re: Why __gthread_active_p() is checked only in few functions?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 30 September 2014 11:17, niXman wrote:
> Jonathan Wakely 2014-09-30 13:22:
>
>> I mean exactly what I wrote.
>>
>> __gthread_mutex_lock is a one-line function that forwards to
>> pthread_mutex_lock. Using GNU libc if you don't link to libpthread.so
>> then pthread_mutex_lock is a no-op function that does nothing. It is
>> quicker to just call it than to spend time checking if threads are
>> active.
>
>
> Ok, but what about '__gthread_mutex_init_function()'?

What part of my first answer wasn't clear? Do I just need to say the
same thing again using different words?




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux