[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [pthreads] performance test using fib.scm
From: |
NIIBE Yutaka |
Subject: |
Re: [pthreads] performance test using fib.scm |
Date: |
Wed, 11 Dec 2002 11:02:14 +0900 (JST) |
Wolfgang Jaehrling wrote:
> 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.
I think that we need some definition of terminology to avoid
confusion. You mean signal protection, with the word "lock", not a
mutex, don't you?
My interpretation:
As malloc is not asynchronous safe, we need to protect calls to it
with signal mask.
IIRC, in Guile implementation, we don't call malloc from interrupt
context, I think we don't have this issue.
--