public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <ross.johnson@homemail.com.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: Re: New pthreads-w32 releases available: versions 2.3.0 and 1.7.0
Date: Fri, 15 Apr 2005 03:08:00 -0000	[thread overview]
Message-ID: <1113534480.9335.411.camel@desk.home> (raw)
In-Reply-To: <OF6A0BC0C8.DF69ABCD-ONC1256FE3.00582DEF-C1256FE3.00597E78@de.ibm.com>

UPDATE: The latest change to pthread_once.c (current CVS head) passes
all the tests on an MP system, particularly the two tests that failed
with release 2.3.0 (each was run hundreds of times). Thanks to Tim
Theisen for running the tests.

This means that people can have more confidence in 2.4.0 when it comes
out (version 1.7.0 still needs to be confirmed but it uses a different
model again - and the original change that caused v2 to fail doesn't
apply to v1).

On Thu, 2005-04-14 at 18:18 +0200, Alexander Terekhov wrote:
> [... named mutex and atrocities of MS impl ...]
> 
> It's not that hard to implement it using a map with pointers (to
> "normal" mutex + refcount structure and addresses of once_control
> variables as keys).

I won't be rushing a version 3 release now unless more problems require
it, but I will pursue this. It would be nice to leave the priority
hacking to the kernel.

As it's turned out, v1 and v2 can be fixed rather than abandoned, as far
as this problem is concerned at least. Other as yet unknown bugs aside,
the version differences are now just in efficiency and, in most
applications, should not even be noticeable.

Thanks.
Ross


      reply	other threads:[~2005-04-15  3:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  7:46 Ross Johnson
2005-04-12 10:10 ` Alexander Terekhov
2005-04-13  7:45   ` Ross Johnson
2005-04-13  8:21     ` Gottlob Frege
2005-04-14 16:19     ` Alexander Terekhov
2005-04-15  3:08       ` Ross Johnson [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1113534480.9335.411.camel@desk.home \
    --to=ross.johnson@homemail.com.au \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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