public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
To: Pthreads-Win32 list <>
Subject: Re: Win64 support, second take
Date: Sat, 27 Jan 2007 01:45:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Direct anonymous access to the pthreads-win32 CVS repository is
described on the project main page at:-

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.

> Cheers,
> Stefan.

  reply	other threads:[~2007-01-27  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 13:47 Stefan Eilemann
2007-01-27  1:45 ` Ross Johnson [this message]
2007-01-29 13:49   ` Streithorst, Kip
2007-01-29 13:54   ` Stefan Eilemann
2007-05-10  8:40 Romanchuk, Mike

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