From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: pthread fast mutexes
Date: Tue, 24 Feb 2004 08:33:49 +1000 [thread overview]
Message-ID: <87wu6dtohe.fsf@zip.com.au> (raw)
In-Reply-To: <xy73c91e9k3.fsf@chunk.mit.edu> (Mikael Djurfeldt's message of "Mon, 23 Feb 2004 17:05:16 -0500")
Mikael Djurfeldt <mdj@mit.edu> writes:
>
> pthread_mutex_unlock unlocks the given mutex. The mutex is assumed to
> be locked and owned by the calling thread on entrance to
> pthread_mutex_unlock.
I suppose it's unspecified what happens if you don't satisfy those
requirements. I seem to get a segv. (glibc 2.3.2, kernel 2.2.15)
Maybe the scheme mutex type will have to make a note of its state or
something, to be sure of obeying the rules.
> BUT, obviously, if these docs don't hold for the fast mutexes on other
> systems, then we can't use them on those systems. How is
> pthread_mutex_unlock for a fast mutyex documented on your system?
I'm not sure where it's supposed to hide on debian. I'm looking at
the linuxthreads/man/*.man pages in the glibc sources. It says what
you said.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-23 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:16 pthread fast mutexes Kevin Ryde
2004-02-23 22:05 ` Mikael Djurfeldt
2004-02-23 22:22 ` Mikael Djurfeldt
2004-02-23 23:46 ` Kevin Ryde
2004-02-24 0:02 ` Mikael Djurfeldt
2004-02-28 20:18 ` Kevin Ryde
2004-03-20 22:51 ` Marius Vollmer
2004-02-23 22:33 ` Kevin Ryde [this message]
2004-02-24 1:17 ` Mikael Djurfeldt
2004-03-20 22:51 ` Marius Vollmer
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=87wu6dtohe.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).