unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Wolfgang Jaehrling <pro-linux@gmx.de>
Cc: guile-devel@gnu.org
Subject: Re: [pthreads] performance test using fib.scm
Date: Tue, 10 Dec 2002 22:10:10 +0100	[thread overview]
Message-ID: <20021210211010.GB355@gmx.de> (raw)
In-Reply-To: <E18LovM-0003lg-00@kvast.blakulla.net>

On Tue, Dec 10, 2002 at 07:16:04PM +0100, Mikael Djurfeldt wrote:
> Still, for large fibonnaci numbers and large branch depths (many
> threads), Guile often crashes in realloc.  That function should be
> thread safe, shouldn't it?

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.

Cheers,
GNU/Wolfgang


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


  reply	other threads:[~2002-12-10 21:10 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 [this message]
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

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=20021210211010.GB355@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).