This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Steven Noonan
Recipients Steven Noonan, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-03-23.13:26:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I originally tagged this issue against 3.6 just because that's what I was attempting to build. But I'm not super concerned about what release these changes actually land in, I can always backport it to my own builds (and at my own risk).

Even though I'm super interested in seeing these changes done, I'm not sure I'm the right person to do the heavy lifting on this. I don't know if the seemingly undocumented (?) Windows ARM64 ABI matches the well-documented Linux AArch64 ABI, for example. If it does match, that would make porting the asm bits pretty straightforward (mostly just translating GNU assembler AT&T syntax to MASM, I suppose). I could do that. But if it doesn't match then I'd probably need to dig into ARM architecture manuals. Someone else could likely do it in their sleep.
Date User Action Args
2018-03-23 13:26:14Steven Noonansetrecipients: + Steven Noonan, paul.moore, tim.golden, zach.ware, steve.dower
2018-03-23 13:26:14Steven Noonansetmessageid: <>
2018-03-23 13:26:14Steven Noonanlinkissue33125 messages
2018-03-23 13:26:14Steven Noonancreate