From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28650 invoked by alias); 17 May 2004 08:24:18 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 28640 invoked from network); 17 May 2004 08:24:13 -0000 Received: from unknown (HELO callisto.canberra.edu.au) (137.92.14.50) by sourceware.org with SMTP; 17 May 2004 08:24:13 -0000 Received: from callisto.canberra.edu.au (nyx.canberra.edu.au [137.92.14.55]) by callisto.canberra.edu.au (8.11.6/8.11.6) with ESMTP id i4H8OA031884 for ; Mon, 17 May 2004 18:24:10 +1000 Message-ID: <40A876EC.3070304@callisto.canberra.edu.au> Date: Mon, 17 May 2004 08:24:00 -0000 From: Ross Johnson Reply-To: rpj@callisto.canberra.edu.au User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040421 MIME-Version: 1.0 CC: pthreads-win32@sources.redhat.com Subject: Re: New snapshot 2004-05-16 available References: <1084779474.40a86bd279418@mail.atlantis.sk> In-Reply-To: <1084779474.40a86bd279418@mail.atlantis.sk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg00065.txt.bz2 Thanks for the quick feedback. ptw32_semwait.c is now in CVS (it is already in the self-extracting zip file on the FTP site but not yet in the tar.gz packages). Also, the version of implement.h in CVS now #defines _WIN32_WINNT 0x400, which should give PAPCFUNC meaning. The makefiles that I use are too helpful - they define _WIN32_WINNT on the CL command line. Ross cameni@manabove.org wrote: >We are having problems compiling source from cvs: > >- seems that ptw32_semwait.c was not added to the cvs >- PAPCFUNC isn't declared when _WIN32_WINNT isn't declared implement.h:449 >- in pthreads_cancel.c:179, the thread->cancelLock isn't unlocked when >WaitForSingleObject returns anything else than WAIT_TIMEOUT (if it terminates >earlier during pthread_cancel) > >brk > > >Ross Johnson wrote: > > >>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. >> >>http://source.redhat.com/pthreads-win32 >>and >>ftp://sources.redhat.com/pub/pthreads-win32 >> >> >>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 >> >>* ptw32_getprocessors() now returns CPU count of 1 for WinCE. >>- James Ewing >> >>* pthread_cond_wait() could be canceled at a point where it should not >>be cancelable. Fixed. >>- Alexander Terekhov >> >>* sem_timedwait() had an incorrect timeout calculation. >>- Philippe Di Cristo >> >>* Fix a memory leak left behind after threads are destroyed. >>- P. van Bruggen >> >> >>New features >> >>* Ported to AMD64. >>- Makoto Kato >> >>* 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. >> >> >> >> > > >