[issue36944] W

2019-05-16 Thread Paul Monson
Change by Paul Monson : -- nosy: Paul Monson priority: normal severity: normal status: open title: W ___ Python tracker <https://bugs.python.org/issue36

[issue36944] Add support for ARM64 to libffi

2019-05-16 Thread Paul Monson
New submission from Paul Monson : These changes are also submitted to libffi as https://github.com/libffi/libffi/pull/490 -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware title: W -> Add support for ARM64 to libffi versions: +Python

[issue36941] Windows build changes for Windows ARM64

2019-05-16 Thread Paul Monson
Change by Paul Monson : -- keywords: +patch pull_requests: +13275 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36941> ___ ___ Py

[issue36942] Windows code changes for Windows ARM64

2019-05-16 Thread Paul Monson
Change by Paul Monson : -- keywords: +patch pull_requests: +13276 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36942> ___ ___ Py

[issue36943] Windows test changes for Windows ARM64

2019-05-16 Thread Paul Monson
Change by Paul Monson : -- keywords: +patch pull_requests: +13277 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue36943> ___ ___ Py

[issue33125] Windows 10 ARM64 platform support

2018-08-08 Thread Paul Monson
Paul Monson added the comment: I'm interested in getting python working on Windows running on Raspberry Pi (Thumb-2 instruction set). I can also contribute to ARM64 Windows. I've made some progress getting ARM32 working on a fork. The next roadblock for my investigation is libf

[issue33125] Windows 10 ARM64 platform support

2018-08-10 Thread Paul Monson
Paul Monson added the comment: The PR hasn't changed since September. Is it still active? Should I consider updating the libffi_msvc code to support ARM32 in Python? Completing the switch to libffi makes more sense to me. I fetched the PR code to my fork and rebased it on the cu

<    1   2