[fix]: fix compile error in torch.compile(fn) when fn is a wrapper of a triton kernel#680
Open
small-cat wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
error in CI, but it is strange, because I can't find any code about |
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
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.
Description
When using torch.compile to compile a graph in vllm-ascend, TorchDynamo throws an exception due to a FlagTree-related issue.
Reproduction
Run the following test case (python test.py):
error
Root Cause
The Triton Ascend backend implementation resides in triton/backends/ascend/spec. TorchDynamo's SKIP_DIRS rule marks the entire triton/backends directory as skipped, causing all definitions under it (including the required Ascend backend code) to be ignored. This leads to the unsupported inline error.
Solution
To improve FlagTree's compatibility with torch.compile, modify the build process to install triton/backends/ascend/spec into triton/ascend instead. This avoids the problematic SKIP_DIRS rule while keeping the code accessible.