Re: [pthreads] performance test using fib.scm

[Christopher Cramer <crayc@pyro.net>]

On Tue, Dec 10, 2002 at 09:10:37PM +0100, Mikael Djurfeldt wrote:
> Wolfgang Jaehrling <pro-linux@gmx.de> writes:
> 
> > malloc() in glibc is thread-save, but not reentrant.  Since the
> > behaviour of realloc() is unlikely to differ from malloc() in this
> > respect, you most certainly have to protect calls to it with a lock.
> 
> 2002-12-10  Mikael Djurfeldt  <mdj@kvast.blakulla.net>
> 
> 	* gc-malloc.c (malloc_mutex): New mutex.
> 	(scm_gc_init_malloc): Initialize it.
> 	(scm_realloc): Serialize call to realloc
> 	(scm_calloc): Same for calloc.
> 	Thanks to Wolfgang Jaehrling!
> 	(Now we have to make sure all calls to malloc/realloc are made
> 	through scm_malloc.)

Every pthreads implementation is required to have a thread-safe malloc,
calloc, realloc and free (along with many other functions). The fact
that malloc etc. are non-reentrant only means that you shouldn't call
them from a signal handler.

Any pthreads implementation that requires you to lock a mutex to call
malloc is broken.

-- 
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
"Gore would have finished ahead by the barest of margins had he pursued
and gained a complete statewide recount." -- Associated Press, 9/6/2002


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel