-
-
Notifications
You must be signed in to change notification settings - Fork 13k
[CPU]Update CPU PyTorch to 2.9.0 #29589
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
Changes from all commits
ea8d4c2
a8da632
122f13f
cb30ccf
d47816f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,9 +4,9 @@ packaging>=24.2 | |
| setuptools>=77.0.3,<81.0.0 | ||
| setuptools-scm>=8 | ||
| --extra-index-url https://download.pytorch.org/whl/cpu | ||
| torch==2.8.0+cpu; platform_machine == "x86_64" or platform_machine == "s390x" | ||
| torch==2.9.0+cpu; platform_machine == "x86_64" or platform_machine == "s390x" | ||
| torch==2.9.0; platform_system == "Darwin" | ||
| torch==2.8.0; platform_machine == "ppc64le" or platform_machine == "aarch64" | ||
| torch==2.9.0; platform_machine == "ppc64le" or platform_machine == "aarch64" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could we hold-off until we check that torch 2.9 works smoothly on Arm? If you need that merged now, please keep the |
||
| scons; platform_machine == "aarch64" # needed to build Arm Compute Library (ACL) | ||
| wheel | ||
| jinja2>=3.1.6 | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -7,17 +7,17 @@ numba == 0.61.2; platform_machine != "s390x" # Required for N-gram speculative d | |
| packaging>=24.2 | ||
| setuptools>=77.0.3,<81.0.0 | ||
| --extra-index-url https://download.pytorch.org/whl/cpu | ||
| torch==2.8.0+cpu; platform_machine == "x86_64" or platform_machine == "s390x" | ||
| torch==2.9.0+cpu; platform_machine == "x86_64" or platform_machine == "s390x" | ||
| torch==2.9.0; platform_system == "Darwin" | ||
| torch==2.8.0; platform_machine == "ppc64le" or platform_machine == "aarch64" | ||
| torch==2.9.0; platform_machine == "ppc64le" or platform_machine == "aarch64" | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. While you've updated the |
||
|
|
||
| # required for the image processor of minicpm-o-2_6, this must be updated alongside torch | ||
| torchaudio; platform_machine != "ppc64le" and platform_machine != "s390x" | ||
|
Comment on lines
+12
to
15
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
On ppc64le we now pin Useful? React with 👍 / 👎.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point, I think we should address this |
||
| torchaudio==2.8.0; platform_machine == "ppc64le" | ||
| torchaudio==2.9.0; platform_machine == "ppc64le" | ||
|
|
||
| # required for the image processor of phi3v, this must be updated alongside torch | ||
| torchvision; platform_machine != "ppc64le" and platform_machine != "s390x" | ||
| torchvision==0.23.0; platform_machine == "ppc64le" | ||
| torchvision==0.24.0; platform_machine == "ppc64le" | ||
| datasets # for benchmark scripts | ||
|
|
||
| # Intel Extension for PyTorch, only for x86_64 CPUs | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why we update to
2.9.0and not2.9.1?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahhh I see @bigPYJ1151 message above saying that other backends are not ready.
Do we know what the issue with
2.9.1is?