From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Mikael Djurfeldt Newsgroups: gmane.lisp.guile.devel Subject: Re: pthread fast mutexes Date: Mon, 23 Feb 2004 20:17:23 -0500 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: References: <87ishxv6m5.fsf@zip.com.au> <87wu6dtohe.fsf@zip.com.au> Reply-To: djurfeldt@nada.kth.se NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1077585875 23923 80.91.224.253 (24 Feb 2004 01:24:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 24 Feb 2004 01:24:35 +0000 (UTC) Cc: djurfeldt@nada.kth.se Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Feb 24 02:24:25 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AvRJA-0000yM-00 for ; Tue, 24 Feb 2004 02:24:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AvRIq-0000y2-8j for guile-devel@m.gmane.org; Mon, 23 Feb 2004 20:24:04 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AvRHX-0000re-8N for guile-devel@gnu.org; Mon, 23 Feb 2004 20:22:43 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AvRFw-00082l-NJ for guile-devel@gnu.org; Mon, 23 Feb 2004 20:21:37 -0500 Original-Received: from [213.212.20.77] (helo=kvast.blakulla.net) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AvRCS-0006Hx-GJ for guile-devel@gnu.org; Mon, 23 Feb 2004 20:17:28 -0500 Original-Received: from witch ([209.150.45.158]) by kvast.blakulla.net with esmtp (Exim 3.36 #1 (Debian)) id 1AvRCP-0007d8-00; Tue, 24 Feb 2004 02:17:25 +0100 Original-Received: from mdj by witch with local (Exim 3.35 #1 (Debian)) id 1AvRCO-0003oY-00; Mon, 23 Feb 2004 20:17:24 -0500 Original-To: guile-devel@gnu.org In-Reply-To: <87wu6dtohe.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 24 Feb 2004 08:33:49 +1000") User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:3446 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:3446 Kevin Ryde writes: > Mikael Djurfeldt 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) I think you're right. I've misinterpreted the docs. I read 'always returns it' without the qualifier 'is assumed to be locked'. > Maybe the scheme mutex type will have to make a note of its state or > something, to be sure of obeying the rules. Since that is a little tricky (would probably need an extra mutex or condition variable to implement it), it might be better to simply use error checking mutexes. >> 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. That's the place to look. (I'll try to verify it in the pthread library sources also.) M _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel