public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
To: Pthreads-Win32 list <>
Subject: Pthreads-win32 - New release 2.8.0 is out now
Date: Fri, 22 Dec 2006 04:05:00 -0000	[thread overview]
Message-ID: <> (raw)

Announcing a new release of pthreads-w32:-

Packages are available in self-unpacking zip files (.exe) and gzipped
tar files (.tar.gz) as usual.


or go directly to:

There may be a low ftp concurrent user limit at the above site.
Mirrors are at:
(available as they update)


New bug fixes in this release since 2.7.0 have not been applied to the
version 1.x.x series. It is probably time to drop version 1.

Testing and verification
This release has not yet been tested on SMP architechtures. All tests pass
on a uni-processor system. If someone can run the test suite on an SMP system,
please let the list know of any success or failure.

Bug fixes
* Sem_destroy could return EBUSY even though no threads were waiting on the 
semaphore. Other races around invalidating semaphore structs (internally)
have been removed as well.

* For WinCE, now checks COREDLL.DLL for InterlockedCompareExchange() instead of
KERNEL32.DLL. This used to be the way it was when the library checked for
TryEnterCriticalSection(), which was removed after that routine was
no longer needed. It was omitted when the technique was resurrected later
for the new purpose. Note: there are no pre-built libs for WinCE.

New tests
semaphore5.c - tests the sem_destroy bug fix referred to above.

             reply	other threads:[~2006-12-22  4:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22  4:05 Ross Johnson [this message]
2006-12-22  4:16 ` Thank you for the bug fixes Sergey Fokin
2006-12-23  1:32 ` Pthreads-win32 - New release 2.8.0 is out now Tim Theisen

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