On 30 September 2014 11:39, Jonathan Wakely <jwakely.gcc@xxxxxxxxx> wrote: > 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? Maybe you can work it out for yourself by seeing if what I wrote about __gthread_mutex_lock applies. Is __gthread_mutex_init_function a one-line function that just forwards to another function?
