Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57414 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84336 invoked from network); 18 Jan 2012 17:38:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Jan 2012 17:38:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=wrowe@rowe-clan.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=wrowe@rowe-clan.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rowe-clan.net from 64.202.165.173 cause and error) X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 64.202.165.173 m1plsmtpa01-01.prod.mesa1.secureserver.net Linux 2.6 Received: from [64.202.165.173] ([64.202.165.173:42771] helo=m1plsmtpa01-01.prod.mesa1.secureserver.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/E1-01828-683071F4 for ; Wed, 18 Jan 2012 12:38:15 -0500 Received: from [192.168.1.199] ([76.252.112.72]) by m1plsmtpa01-01.prod.mesa1.secureserver.net with id P5eA1i00M1Zmh9Y015eBTx; Wed, 18 Jan 2012 10:38:11 -0700 Message-ID: <4F170372.2080201@rowe-clan.net> Date: Wed, 18 Jan 2012 11:37:54 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Lester Caine CC: PHP internals References: <4F16AB37.1070107@lsces.co.uk> <4F16B758.7010206@lsces.co.uk> In-Reply-To: <4F16B758.7010206@lsces.co.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 64bit Windows builds From: wrowe@rowe-clan.net ("William A. Rowe Jr.") On 1/18/2012 6:13 AM, Lester Caine wrote: > > A much better reason for not supporting the build is probably that the 64bit compiler is > not available in the free development stack? We have to buy a development stack to get the > 64bit compiler which blocks rather than working with the publicly available process :( > But actually that is a better reason for supplying a 64 bit build, and why others are > providing that service. Actually, no. There are any number of free mechanisms to build 64 bit code. The root problem is that Windows "WIN64" is a 64P architecture. Linux and *nix variants, on the other hand, are 64ILP or 64LP. Meaning Windows has longs/ints which are undersized compared to the *nix brethren. The old and stale abuse such as unsigned long X = (unsigned long)pY; will not do what the author intended. This means all packages ported to *nix 64 bits may have very serious flaws which have not been fixed for *Windows 64 bit* architecture. I'd anticipate CoApp identifying and resolving most of these applicable to PHP over the coming months, but it is a non-trivial problem requiring a number of pairs of eyeballs to get right.