From: Linas Vepstas <INVALID.NOREPLY@gnu.org>
To: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>,
"Linas Vepstas" <linasvepstas@gmail.com>,
bug-guile@gnu.org
Subject: [bug #24867] `define' should be thread-safe
Date: Tue, 23 Dec 2008 18:28:47 +0000 [thread overview]
Message-ID: <20081223-182846.sv71519.10756@savannah.gnu.org> (raw)
In-Reply-To: <20081223-152123.sv15145.27370@savannah.gnu.org>
Follow-up Comment #5, bug #24867 (project guile):
1) Easier said than done, because:
1a) the mutex needs to be recursive, since sym2var evaluates code in
boot9.scm which can cause sym2var to run again. The core problem is that the
mechanism for specifying recursive mutexes seems to be somewhat OS-dependent
(and possibly some OS'es don't support recursive mutexes??) and so a
portability wrapper might be needed. :-(
1b) There's still a strange deadlock somehow; am debugging.
3) Fine-grained usually means speedy. *if* there was some per-module C
struct, then the mutex could be put in there. (I don't know of any, but I
don't know guile internals). The alternative would be somehow grabbing a lock
in the boot9.scm code, but I don't see how, without making some symbol lookup
(i.e. race).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24867>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2008-12-23 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 10:18 [bug #24867] `define' should be thread-safe Ludovic Courtès
2008-11-18 13:27 ` Ludovic Courtès
2008-12-23 2:36 ` Linas Vepstas
2008-12-23 2:50 ` Linas Vepstas
2008-12-23 3:06 ` Linas Vepstas
2008-12-23 15:21 ` Ludovic Courtès
2008-12-23 18:28 ` Linas Vepstas [this message]
2008-12-23 19:10 ` Linas Vepstas
2010-09-20 9:28 ` Kourtney Keese
2011-08-06 9:08 ` JackBenny
2011-08-06 9:08 ` JackBenny
2011-08-06 9:09 ` JackBenny
2011-08-06 9:09 ` JackBenny
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=20081223-182846.sv71519.10756@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=linasvepstas@gmail.com \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).