-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Enable Windows Arm64 #133088
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Windows Arm64 #133088
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/133088
Note: Links to docs will display an error until the docs builds have been completed. ❌ 7 New Failures, 4 Unrelated FailuresAs of commit 69df17a with merge base 2827bef ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
ad01da5 to
560d828
Compare
|
@malfet you've got this one? |
Yeah, I waited for some reference to upstream issue why this is needed |
|
@pytorchbot merge -f "It probably works" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
This PR enables Pytorch for Windows on Arm64 - CPU only.
Currently, there aren't any checks in place to build and test for Windows on Arm64, but we're working to implement those as soon as possible.
We recommend using Arm Performance Libraries (APL) as a BLAS option, which is introduced in this PR.
cc @peterjc123 @mszhanyi @skyline75489 @nbcsm @Blackhex @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @voznesenskym @penguinwu @EikanWang @Guobing-Chen @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov