From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Terrific Dead Lock
Date: Wed, 16 Apr 2008 12:03:55 +0200 [thread overview]
Message-ID: <87tzi2yv3o.fsf@gnu.org> (raw)
In-Reply-To: 87ve2i4yl8.fsf@ossau.uklinux.net
Hi,
Neil Jerram <neil@ossau.uklinux.net> writes:
> Yes, fine. Sorry for forgetting about this.
Thanks, applied.
> (I wonder if SCM_CDR (scm_last_plist_filename) on one thread is
> guaranteed to give a sane value, if there is another thread
> simultaneously doing SCM_SETCDR (scm_last_plist_filename) - but I'm
> not an expert in this kind of thing.)
Yes, I suppose that's the assumption, and it's probably a reasonable one
since `SCM_SETCDR' boils down to a single memory write.
Thanks,
Ludovic.
next prev parent reply other threads:[~2008-04-16 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 22:29 Terrific Dead Lock Ludovic Courtès
2008-03-14 10:24 ` Ludovic Courtès
2008-03-17 23:20 ` Neil Jerram
2008-03-18 21:20 ` Ludovic Courtès
2008-04-14 14:29 ` Ludovic Courtès
2008-04-15 21:06 ` Neil Jerram
2008-04-16 10:03 ` Ludovic Courtès [this message]
2008-04-16 20:29 ` Neil Jerram
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=87tzi2yv3o.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).