Repository navigation
Add support for Windows on ARM64 #1
Description
Hello,
I am trying to use greenlet with Python 3.8 / 3.9 on Windows ARM64, but there is a compilation issue when I try building it using VS Studio 2017 / 2019, as there is no support. Do you have any pointers on how this can be achieved?
I have also opened python-greenlet/greenlet#220 for guidance.
Thank you,
Adrian
Activity
kristjanvalur commentedon Nov 24, 2020
Unfortunately I have not touched the greenlet project for a long time. The stack slicing code split up years ago from Stackless python into the Greenlet project.
I have already done this for the "stackman" project. I would suggest that you look at the difference between the ARM and ARM32 code here in this repository (the switch_arm_gcc.h and the switch_aarch64_gcc.h) look at the differences, and apply similar changes to the greenlet, creating a switcg_aarch64_gcc.h there.
The switching code cannot be taken directly since the arguments are slightly different. It will be mostly a case of renaming the registers (from r to x) and noticing the different register numbers that need to be preserved across calls for both architectures.
kristjanvalur commentedon Nov 24, 2020
Another approach would be to create a shim, and actually use the stackman project here. I aim to actually submit the libs for the different arthcitectures into the repository.
In the stackless project, I made a PR that illustrates how the slp_switch() function can be implemented in terms of stackman_switch():
stackless-dev/stackless#230
Ideally, when I manage to make this project stable and have released libs available for all major platforms, projects like stackless and greenlets can actually just link with the comman code here.
I still haven't finished windows support for stackman, though. And I don't support any of the legacy platforms. Only arm, x86linux and x86 windows. (32 and 64) bits.
kristjanvalur commentedon Nov 29, 2020
Hm, I see that you speak of windows/arm64. This is new to me. I have to finalize windows/86 support in this lib first, then maybe if I can get access to an ARM64 win machine....
kristjanvalur commentedon Apr 5, 2021
windows support for X86/64 bit is complete, and theoretically it should also work for windows 10 on aarch64, but I have not had access to such a platform to test.
Merge pull request #1 from kristjanvalur/dev
kristjanvalur commentedon Sep 8, 2024
Github will be adding arm64 support by the end of the year to open source repos. i'll update the tealet repo to test the stackman code on windows 64 once that happens.
https://github.blog/news-insights/product-news/arm64-on-github-actions-powering-faster-more-efficient-build-systems/
kristjanvalur commentedon Oct 16, 2026
Closing this. Windows ARM64 is a supported ABI in this repository.
win_arm64is implemented bystackman/platforms/switch_arm64_msvc.asmandswitch_arm64_msvc.h.platform.hselects it for_M_ARM64. The namewin_aarch64is accepted and normalized towin_arm64. The VS2022 solution builds it, and.github/workflows/buildcommit.ymlbuildsPlatform=arm64on every pull request. The 1.3.0 sources spillFPCRandFPSRthere and keep the TEB registerx18restored rather than using it as a scratch.The arm64 job is a cross build, so CI does not execute
test.exeon Windows ARM64. The implementation and the build are what this issue asked for. Runtime coverage on that OS is still the x86 and x64 jobs.The other open items stay open. Stack overflow helpers are still only a proposal (#14).
STACKMAN_HAVE_CALLis removed in a separate change, aimed at 1.4.0 (#16).