[xpu][fix] Change min_dot_size call due to Triton API Change #1173
Conversation
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
meta-cla
bot
added
the
CLA Signed
This was referenced Nov 28, 2025
EikanWang
reviewed
Nov 28, 2025
| from triton.backends.intel.compiler import min_dot_size as min_dot_size_xpu | ||
| try: | ||
| # Support New triton API which put the min_dot_size in XPUBackend class | ||
| from triton.backends.intel.compiler import XPUBackend |
Collaborator
There was a problem hiding this comment.
CUDA does not do it. I'm wondering why we need to do it. @etiotto, may I know the background?
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.
This PR is to align with the XPU Triton recently change. Now the
min_dot_size()call is not exposed directly and wrapped inXPUBackendclass according to intel/intel-xpu-backend-for-triton#5329.cc: @EikanWang