Re: lock, tls, and single-threaded applications

2008-06-18 Thread Bruno Haible
Jim Meyering wrote: > That has made me consider (if/when sort does become > multithreaded) building specified multithreaded programs in > coreutils against a separate thread-safe gnulib instance, > so that the remaining 100 programs don't suffer just because > sort flipped the MT switch. Makes sen

Re: lock, tls, and single-threaded applications

2008-06-18 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote: > Eric Blake wrote: >> Next I'm wondering if we should add a module which invokes >> gl_DISABLE_THREADS, as well as pulls in the unlocked-io module, for the >> benefit of projects that are known to be single-threaded, as it is >> slightly easier to add a modu

Re: lock, tls, and single-threaded applications

2008-06-18 Thread Bruno Haible
Eric Blake wrote: > Next I'm wondering if we should add a module which invokes > gl_DISABLE_THREADS, as well as pulls in the unlocked-io module, for the > benefit of projects that are known to be single-threaded, as it is > slightly easier to add a module to the list of imports than it is to > modi

Re: lock, tls, and single-threaded applications

2008-06-17 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 6/17/2008 6:33 PM: | | But these header files are already providing no-op code if the user has | chosen to configure with --disable-threads. The default for this option is in | m4/lock.m4, lines 49..55. lock.m4 can export

Re: lock, tls, and single-threaded applications

2008-06-17 Thread Bruno Haible
Hi Eric, > The strsignal module is rather heavy-handed when used for a single-threaded > app, since thread-local storage is not really necessary in that case. What > is > the recommended way to git a single-thread-friendly strsignal? Maybe it is > worth creating a strsignal-simple module tha