From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1822 invoked by alias); 27 Jan 2007 01:45:27 -0000 Received: (qmail 1812 invoked by uid 22791); 27 Jan 2007 01:45:26 -0000 X-Spam-Check-By: sourceware.org Received: from canyonero.dot.net.au (HELO canyonero.dot.net.au) (202.147.68.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 27 Jan 2007 01:45:16 +0000 Received: from [203.129.41.210] (helo=[203.129.41.210]) by canyonero.dot.net.au with esmtp (Exim 3.35 #1 (Debian)) id 1HAccw-0004M3-00 for ; Sat, 27 Jan 2007 12:45:11 +1100 Message-ID: <45BAAEA5.8040408@homemail.com.au> Date: Sat, 27 Jan 2007 01:45:00 -0000 From: Ross Johnson User-Agent: Thunderbird 1.5.0.7 (X11/20061008) MIME-Version: 1.0 To: Pthreads-Win32 list Subject: Re: Win64 support, second take References: <416E6645-296B-4F44-B475-BEA2A939C72F@gmail.com> In-Reply-To: <416E6645-296B-4F44-B475-BEA2A939C72F@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2007/txt/msg00008.txt.bz2 Stefan Eilemann wrote: > Keith, List, > > I have seen your posting from March 2006 regarding Win64 support. > I am in the need of a Win64 port -- has anybody in the meantime > successfully build a libpthread on Win64, or is the code in more > or less the same state? > The current CVS head contains some additional changes for Win64 build and test provided by Kip, who subsequently reported that he could now build and complete all tests, although there were warnings:- Kip wrote:- "2. Since you are using /WX, the tests fail as soon as Visual Studio outputs a warning, it currently outputs two different warnings, one is related to _ftime64 being deprecated, which I can suppress by including /D_CRT_SECURE_NO_DEPRECATE in the CFLAGS variable. The other is more troublesome, there are about 20-30 places in the tests where you copy a value of the _timeb structure into the timespec structure. The problem with that is in 64-bit mode, most of the values of the _timeb structure are 64-bit integers (ie. __time64_t) and the timespec structure only holds 32-bit integers (ie. long) and Visual Studio issues a warning about truncating the numbers during the assignment. Any suggestions on what fix should be applied here?" The _timeb issue has not been properly resolved, although I'm guessing it is not a problem yet. AFAICS the structure elements still represent the same time components with the same epoch as the 32 bit version, and no actual truncation is taking place. I'm assuming that 2038 is still the critical year for this. Please correct me if that understanding is wrong. Direct anonymous access to the pthreads-win32 CVS repository is described on the project main page at:- http://sourceware.org/pthreads-win32/ I plan to package the next version 2.9 of the library once I've reviewed and included some more WinCE changes, but my day job is a little full-on at the moment. Regards. Ross > > Cheers, > > Stefan.