public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: RE: pthreads-w32 2.2.0 test failures
Date: Tue, 05 Apr 2005 06:03:00 -0000	[thread overview]
Message-ID: <1112680993.15352.178.camel@desk.home> (raw)
In-Reply-To: <1E2E66102E75104D8C740340EBCD9867144A37@tomoex.tomotherapy.com>

On Mon, 2005-04-04 at 22:59 -0500, Tim Theisen wrote:
> I agree with your assessment.  Those tests need improvement.

I've visually checked all the tests for this problem and those listed
below have been modified. They'll be committed to CVS after I've booted
into Windows and run them.

cleanup0.c
cleanup1.c
cleanup2.c
cleanup3.c
once2.c
once3.c

Obviously the same problem or two has been inherited down the line. New
tests are added by taking an old one as a template.

Are there any other specific improvements you think are needed?

> At least you know someone is giving pthreads-w32 a run for its
> money on a multiprocessor system.

It may be awhile before I get one myself. So please do.

Thanks.
Ross

> ...Tim
> 
> -----Original Message-----
> From: pthreads-win32-owner@sources.redhat.com
> [mailto:pthreads-win32-owner@sources.redhat.com]On Behalf Of Ross
> Johnson
> Sent: Monday, April 04, 2005 21:06
> To: Pthreads-Win32 list
> Subject: Re: pthreads-w32 2.2.0 test failures
> 
> 
> All of these are unserialised shared global variables in the tests
> themselves!! Sketchy test coding that didn't show up on my single
> processor.
> 
> Almost certain it's not a problem with the library.
> 
> Thanks.
> Ross
> 

  reply	other threads:[~2005-04-05  6:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05  3:59 Tim Theisen
2005-04-05  6:03 ` Ross Johnson [this message]
2005-04-05  7:03 ` Steve Croall
2005-04-05 16:03   ` Ross Johnson
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05 12:50 Tim Theisen
2005-04-04 21:49 Tim Theisen
2005-04-04 21:41 Tim Theisen
2005-04-05  2:06 ` 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:
  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=1112680993.15352.178.camel@desk.home \
    --to=rpj@callisto.canberra.edu.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).