unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Using define in multiple threads?
Date: Mon, 17 Nov 2008 15:57:06 +0100	[thread overview]
Message-ID: <87od0ee6yl.fsf@gnu.org> (raw)
In-Reply-To: gfrqvq$os6$1@ger.gmane.org

Hey!

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> Linas Vepstas escreveu:
>> Is it "safe" or "legal" to use define in multiple threads?
>
> I guess not.  Someone -I forgot who- put in the pthreads without thinking 
> through the consequences.
>
> Look through eval.c, you´ll see
>
>   SCM_SETCAR (expr, SCM_IM_DO);
>   // *
>   SCM_SETCDR (expr, tail);
>
> which is very dubious if a thread switch happens at (*)

You're answering a more general question: "is it safe to evaluate code
in multiple threads?".  I'm afraid your answer is correct, but, if it
happens that the code to be evaluated has already been memoized, then
everything's alright.  Thankfully, the VM will soon save us from this.
:-)

Besides, as Linas noted, the hash table implementation isn't
thread-safe, which makes it "unsafe" to `define' in parallel.

Thanks,
Ludo'.





  reply	other threads:[~2008-11-17 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 22:27 Using define in multiple threads? Linas Vepstas
2008-11-17 13:18 ` Han-Wen Nienhuys
2008-11-17 14:57   ` Ludovic Courtès [this message]
2008-11-17 20:45     ` Andy Wingo
2008-11-18 10:20       ` Ludovic Courtès
2008-11-19 23:36         ` Neil Jerram
2008-11-19 23:45           ` Andy Wingo
2008-11-20  8:33             ` Ludovic Courtès

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=87od0ee6yl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /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).