Skip to content

Add CUDA 13.2 support and drop unsupported 12.8/12.9#20440

Merged
Gasoonjia merged 2 commits into
mainfrom
cuda-13.2-support
Jun 25, 2026
Merged

Add CUDA 13.2 support and drop unsupported 12.8/12.9#20440
Gasoonjia merged 2 commits into
mainfrom
cuda-13.2-support

Conversation

@Gasoonjia

Copy link
Copy Markdown
Contributor

Add (13, 2) to SUPPORTED_CUDA_VERSIONS in install_utils.py and to the cuda.yml build matrix. Remove 12.8 and 12.9, which are no longer supported.

Add (13, 2) to SUPPORTED_CUDA_VERSIONS in install_utils.py and to the cuda.yml build matrix. Remove 12.8 and 12.9, which are no longer supported.
@pytorch-bot

pytorch-bot Bot commented Jun 23, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/20440

Note: Links to docs will display an error until the docs builds have been completed.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 23, 2026
@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@Gasoonjia Gasoonjia merged commit c0643f5 into main Jun 25, 2026
222 of 229 checks passed
@Gasoonjia Gasoonjia deleted the cuda-13.2-support branch June 25, 2026 22:28
Gasoonjia added a commit that referenced this pull request Jun 26, 2026
…failure

The Windows CI image ships CUDA toolkits on PATH. After adding (13, 2) to
SUPPORTED_CUDA_VERSIONS (#20440), install_executorch's auto-detection
(setup.py: is_cuda_available() via nvcc) started returning True on the Windows
runner (which has the CUDA 13.2 toolkit), so it flipped EXECUTORCH_BUILD_CUDA=ON.
But the unittest jobs install CPU torch, so the resulting CUDA build of
_portable_lib fails to load its CUDA DLLs at import time:

  ImportError: DLL load failed while importing _portable_lib

causing all pytest collection to error out (unittest / unittest-editable /
unittest-release on windows).

Add a -cpuOnly switch to setup-windows.ps1 that forces
-DEXECUTORCH_BUILD_CUDA=OFF via CMAKE_ARGS, and pass it from the CPU unittest
workflow. The CUDA Windows jobs (cuda-windows.yml) keep the default and are
unaffected.
Gasoonjia added a commit that referenced this pull request Jun 26, 2026
…LL load failure

Same root cause as the unittest fix in this PR, second site. The Windows wheel
build (build-wheels-windows.yml -> .ci/scripts/wheel/) does not go through
setup-windows.ps1. The Windows CI image has the CUDA 13.2 toolkit on PATH, so
after #20440 added (13, 2) to SUPPORTED_CUDA_VERSIONS, install_executorch's
auto-detection enables EXECUTORCH_BUILD_CUDA and bakes a CUDA _portable_lib +
aoti_cuda_shims.lib into the CPU wheel. The smoke test then fails with:

  ImportError: DLL load failed while importing _portable_lib

Windows wheels are CPU-only (with-cuda: disabled), so force
-DEXECUTORCH_BUILD_CUDA=OFF via CMAKE_ARGS in pre_build_script.sh on Windows.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/cuda CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants