XPU: Add oneAPI 2026 build; package both 2025 and 2026 variants#2002
Merged
Conversation
Member
Author
|
cc @jiqing-feng if you don't mind trying this out! |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
Contributor
|
It works well on my local node: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We currently build our SYCL XPU kernels on both Linux and Windows using oneAPI 2025.1. Since oneAPI 2026.0 has been released and PyTorch has migrated to 2026.0.0, we need to provide compatibility across these major versions.
This PR makes the following changes:
torch.version.xputo determine which library to try and load to ensure we're compatible with the major version used for PyTorch.Resolves #1991