This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ANSI/IEEE POSIX 1003.1 and GCC (+ Other GNU)

From: Richard Henderson <rth at redhat dot com>
To: Takis Psarogiannakopoulos <takis at XFree86 dot Org>
Cc: gcc at gcc dot gnu dot org, mark at codesourcery dot com
Date: Thu, 07 Jan 2010 13:06:13 -0800
Subject: Re: ANSI/IEEE POSIX 1003.1 and GCC (+ Other GNU)
References: <20100107013727.A77252@public.xfree86.org>

On 01/07/2010 01:59 AM, Takis Psarogiannakopoulos wrote:

The right thing to do is use the depth (count above) of the mutex to
decide if the mutex is free. The owner shoud be valid only if the mutex is
locked.


I believe the following should fix this for you, at least for libgomp.
If you have a system for which the thread-id 0 is actually used, would
you mind testing it?

r~

Attachment: z
Description: Text document

Follow-Ups:
- Re: ANSI/IEEE POSIX 1003.1 and GCC (+ Other GNU)
  - From: Eric Botcazou

References:
- ANSI/IEEE POSIX 1003.1 and GCC (+ Other GNU)
  - From: Takis Psarogiannakopoulos

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]