delorie.com/archives/browse.cgi | search |
On Sat, Apr 21, 2001 at 01:38:58PM -0400, Charles S. Wilson wrote: >Didn't somebody already do a threadsafeness audit of newlib? If so, >then we don't want to break threadsafeness with these changes. I'm not >familiar with threaded code in C; what is neccessary to insure that a >given function is both reentrant and threadsafe (if a block of code is >threadsafe it is automatically reentrant, but a reentrant block is not >necessarily threadsafe, right?) That's right. AFAIK, newlib is not guaranteed to be thread safe. So, I guess that Cygwin is, by extension, not really thread safe either. I can think of a few functions in cygwin that are not thread safe, in fact. The enviroment manipulation is not thread-safe. I don't believe that vfork is thread safe. I'm sure that there are many others. cgf
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |