From: Wolfgang Jaehrling <pro-linux@gmx.de>
Cc: guile-devel@gnu.org
Subject: Re: [pthreads] performance test using fib.scm
Date: Wed, 11 Dec 2002 18:27:09 +0100 [thread overview]
Message-ID: <20021211172709.GA247@gmx.de> (raw)
In-Reply-To: <200212110202.gBB22Et27423@mule.m17n.org>
On Wed, Dec 11, 2002 at 11:02:14AM +0900, NIIBE Yutaka wrote:
> 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?
Yes. However, that malloc() in glibc is thread-save does not imply
that this is the case for other libc:s as well, so a mutex _might_
still be necessary for some systems. If guile does not call malloc()
(or realloc()) from a signal handler, then it is supposed to not be a
problem for GNU/Linux and GNU/Hurd (and other systems using glibc).
Cheers,
GNU/Wolfgang
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2002-12-11 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:16 [pthreads] performance test using fib.scm Mikael Djurfeldt
2002-12-10 21:10 ` Wolfgang Jaehrling
2002-12-10 20:10 ` Mikael Djurfeldt
2002-12-11 20:05 ` Christopher Cramer
2002-12-11 5:02 ` Maciej Stachowiak
2002-12-11 7:11 ` Mikael Djurfeldt
2002-12-11 13:48 ` Maciej Stachowiak
2002-12-11 23:43 ` Han-Wen Nienhuys
2002-12-11 16:59 ` Wolfgang Jaehrling
[not found] ` <200212110202.gBB22Et27423@mule.m17n.org>
2002-12-11 17:27 ` Wolfgang Jaehrling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021211172709.GA247@gmx.de \
--to=pro-linux@gmx.de \
--cc=guile-devel@gnu.org \
--cc=wolfgang@pro-linux.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).