| delorie.com/archives/browse.cgi | search |
| X-Recipient: | archive-cygwin AT delorie DOT com |
| X-Spam-Check-By: | sourceware.org |
| Date: | Sat, 30 Jul 2011 12:22:49 +0200 |
| From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
| To: | cygwin AT cygwin DOT com |
| Subject: | Re: Pthread error? |
| Message-ID: | <20110730102249.GJ26203@calimero.vinschen.de> |
| Reply-To: | cygwin AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| References: | <CADqjQ-J73y4M18LJH9a84VUZ+Pj8JsphW9SX9TDuLgd2YJ0aAg AT mail DOT gmail DOT com> <CADqjQ-KN6xUZdUwY-ZBvn91anFjyKb_=Rya3w5v25oJwPKRruQ AT mail DOT gmail DOT com> <CADqjQ-KwXX7cPpqNtHyCseZ_u1h5AuGrAAfVZPA-ofiKg3QMFQ AT mail DOT gmail DOT com> <CADqjQ-J4_nu1-0EZWVD0ZEaCkjxrw5bbuxUJ1DbxbJd2Cqdd7w AT mail DOT gmail DOT com> |
| MIME-Version: | 1.0 |
| In-Reply-To: | <CADqjQ-J4_nu1-0EZWVD0ZEaCkjxrw5bbuxUJ1DbxbJd2Cqdd7w@mail.gmail.com> |
| User-Agent: | Mutt/1.5.21 (2010-09-15) |
| Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
| List-Id: | <cygwin.cygwin.com> |
| List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
| List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
| List-Archive: | <http://sourceware.org/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT cygwin DOT com> |
| List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
| Sender: | cygwin-owner AT cygwin DOT com |
| Mail-Followup-To: | cygwin AT cygwin DOT com |
| Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Jul 30 05:52, Jan Chludzinski wrote:
> > pthread_getthreadid_np is a non-standard IBM extension. You won't find
> > it in the POSIX specs.
>
> Does Cygwin support the full POSIX pthread spec?
That would be nice, but, no, not yet. See
http://cygwin.com/cygwin-api/compatibility.html
In the next Cygwin version 1.7.10, most of the missing pthread functions
from http://cygwin.com/cygwin-api/std-notimpl.html will have been added.
Still missing for 1.7.10 since nobody implemented them yet are
pthread_barrier[...]
pthread_mutexattr_getrobust
pthread_mutexattr_setrobust
pthread_mutex_consistent
pthread_mutex_timedlock
pthread_rwlock_timedrdlock
pthread_rwlock_timedwrlock
In theory, except for the barrier functions, they shouldn't be very hard
to implement.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |