Re: [pypy-dev] Fwd: [#3588935] Re: PyPy 3 for Windows 64-bit systems
Dear Brian The Wikipedia article seems to imply that using Cygwin as a compiler on Windows 64 would resolve the problem? Dear Armin, it can't be possibly that easy? Best regards Martin
From what I understand the underlying cause is because 64bit windows (or more specifically the visual studio C compiler) uses an LLP64 (IL32P64) data model* while most 64bit unix based systems use LP64 (I32LP64).
The previously linked article on getting a 64bit windows pypy talks about the size difference for long but doesn't spell out the data model explicitly.
Hopefully that helps clear up where the underlying issue comes from.
Brian Haskin
* https://en.wikipedia.org/wiki/64-bit_computing#64-bit_data_models
Hi, On Thu, 25 Oct 2018 at 16:48, <Martin.Gfeller@swisscom.com> wrote:
The Wikipedia article seems to imply that using Cygwin as a compiler on Windows 64 would resolve the problem?
It might, but then you would have to compile all the CPython C extension modules using Cygwin as well, which is (1) unexpected and (2) likely to break some of them not expecting a different 64-bit model. In addition, I have no clue about which calling convention Cygwin-on-64bit-Windows is using, which is important for our JIT. So no, that's unlikely to be the right approach to 64-bit Windows. A bientôt, Armin.
Hi, On Thu, 25 Oct 2018 at 16:48, <Martin.Gfeller@swisscom.com> wrote:
The Wikipedia article seems to imply that using Cygwin as a compiler on Windows 64 would resolve the problem?
It might, but then you would have to compile all the CPython C extension modules using Cygwin as well, which is (1) unexpected and (2) likely to break some of them not expecting a different 64-bit model. In addition, I have no clue about which calling convention Cygwin-on-64bit-Windows is using, which is important for our JIT. So no, that's unlikely to be the right approach to 64-bit Windows. A bientôt, Armin.
participants (2)
-
Armin Rigo -
Martin.Gfeller＠swisscom.com