Skip to content

Commit dab3b0e

Browse files
ZhaoqiongZsekyondaMetazeshengzong
committed
fix link for tutorial of inductor on windows (pytorch#159853)
fix link issue from https://docs.pytorch.org/tutorials/prototype/inductor_windows.html to https://docs.pytorch.org/tutorials/unstable/inductor_windows.html due to structure change with pr pytorch/tutorials#3489 Pull Request resolved: pytorch#159853 Approved by: https://github.com/sekyondaMeta Co-authored-by: sekyondaMeta <[email protected]> Co-authored-by: Zesheng Zong <[email protected]>
1 parent ba56102 commit dab3b0e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/source/notes/get_start_xpu.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ If you are migrating code from ``cuda``, you would change references from ``cuda
107107
The following points outline the support and limitations for PyTorch with Intel GPU:
108108

109109
#. Both training and inference workflows are supported.
110-
#. Both eager mode and ``torch.compile`` is supported. The feature ``torch.compile`` is also supported on Windows from PyTorch* 2.7 with Intel GPU, refer to `How to Use Inductor on Windows with CPU/XPU <https://pytorch.org/tutorials/prototype/inductor_windows.html>`_.
110+
#. Both eager mode and ``torch.compile`` is supported. The feature ``torch.compile`` is also supported on Windows from PyTorch* 2.7 with Intel GPU, refer to `How to use torch.compile on Windows CPU/XPU <https://pytorch.org/tutorials/unstable/inductor_windows.html>`_.
111111
#. Data types such as FP32, BF16, FP16, and Automatic Mixed Precision (AMP) are all supported.
112112

113113
Examples

0 commit comments

Comments
 (0)