public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
Subject: New snapshot 2004-05-16 available
Date: Mon, 17 May 2004 06:05:00 -0000	[thread overview]
Message-ID: <> (raw)

Dear all,

Finally there is a new snapshot available that incorporates 99 percent 
of the issues raised over the past 8 to 9 months, including some that 
had not made it into CVS until today.

Here are the main changes:

SNAPSHOT 2004-05-16

Attempt to add Watcom to the list of compilers that can build the library.
This failed in the end due to it's non-thread-aware errno. The library
builds but the test suite fails. See README.Watcom for more details.

Note: This is probably a result of not defining the appropriate macro.

Bug fixes

* Bug and memory leak in sem_init()
- Alex Blanco  <Alex.Blanco at>

* ptw32_getprocessors() now returns CPU count of 1 for WinCE.
- James Ewing  <james.ewing at>

* pthread_cond_wait() could be canceled at a point where it should not
be cancelable. Fixed.
- Alexander Terekhov  <TEREKHOV at>

* sem_timedwait() had an incorrect timeout calculation.
- Philippe Di Cristo  <philipped at>

* Fix a memory leak left behind after threads are destroyed.
- P. van Bruggen  <pietvb at>

New features

* Ported to AMD64.
- Makoto Kato  <raven at>

* True pre-emptive asynchronous cancelation of threads. This is optional
and requires that Panagiotis E. Hadjidoukas's QueueUserAPCEx package be
installed. This package is included in the pthreads-win32 self-unpacking
Zip archive starting from this snapshot. See the README.txt file inside
the package for installation details. Many thanks to Panagiotis for his
assistance in getting the hooks into the library.

Note: If you don't use async cancelation in your application, or don't need
to cancel threads that are blocked on system resources such as network I/O,
then the default non-preemptive async cancelation is probably good enough.
However, pthreads-win32 auto-detects the availability of these components
at run-time, so you don't need to rebuild the library from source if you
change your mind later.

All of the advice available in books and elsewhere on the undesirability
of using async cancelation in any application still stands, but this
feature is a welcome addition with respect to the library's conformance to
the POSIX standard.

             reply	other threads:[~2004-05-17  6:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17  6:05 Ross Johnson [this message]
2004-05-17  7:36 cameni
2004-05-17  7:42 ` Dr. Michael Heitland (caatoosee ag)
2004-05-17  8:24 ` Ross Johnson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).