You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[torch] Enable stable torch 2.9 builds on Windows and update docs (#1809)
## Motivation
Fixes#1677, filling in the latest
support matrix for supported PyTorch versions for our nightly release
builds. I also took the opportunity to clarify and refresh the
documentation.
## Technical Details
For now this uses `release/2.9_rocm7.9`. Depends on
ROCm/pytorch#2712 to use `release/2.9`.
## Test Plan
Trigger test release builds using
https://github.com/ROCm/TheRock/actions/workflows/release_windows_pytorch_wheels.yml
- [ ] Test `release/2.9` once that PR is merged
- [x] Test `release/2.9_rocm7.9`:
https://github.com/ROCm/TheRock/actions/runs/18598633844
## Test Results
Test release builds completed and sanity checks passed.
| Flash attention via [ao]triton | ✅ Supported for torch 2.7<br>❌ Not yet supported for newer versions (see [Issue#1408](https://github.com/ROCm/TheRock/issues/1408)) | ✅ Supported since torch 2.9 |
39
37
40
38
### Supported PyTorch versions
41
39
42
-
We support building ROCm source and nightly releases together with several
43
-
different PyTorch versions. The intent is to support the latest upstream PyTorch
44
-
code (i.e. `main` or `nightly`) as well as recently published release branches
45
-
which users depend on. Developers can also build variations of these versions to
46
-
suite their own requirements.
40
+
We support building various PyTorch versions compatible with the latest ROCm
41
+
sources and release packages.
42
+
43
+
Support for the latest upstream PyTorch code (i.e. `main` or `nightly`) uses the
44
+
upstream projects directly, while extended support for older releases is maintained
45
+
via backported release branches in https://github.com/ROCm/pytorch. Developers can
46
+
also build variations of these versions to suite their own requirements.
47
+
48
+
> [!NOTE]
49
+
> We build "nightly" versions with alpha suffixes. Once
50
+
> PyTorch promotes a new release version, we switch from the upstream branches
51
+
> to the backported release branches in https://github.com/ROCm/pytorch without
52
+
> such version suffixes (e.g. `2.7.0a0`-> `2.7.1`).
53
+
>
54
+
> Historical builds are archived at https://rocm.nightlies.amd.com according to
55
+
> some retention policy.
47
56
48
57
Each PyTorch version uses a combination of:
49
58
50
59
- Git repository URLs for each project
51
60
- Git "repo hashtags" (branch names, tag names, or commit refs) for each project
52
61
- Optional patches to be applied on top of a git checkout
53
62
54
-
See the following table for how each version is supported. Previously supported
55
-
versions are no longer being built but may have existing wheels in the
0 commit comments