[OpClassifier](fix) share cube upstream skip rules across both BFS paths - #1531
Open
245516766 wants to merge 1 commit into
Open
[OpClassifier](fix) share cube upstream skip rules across both BFS paths#1531245516766 wants to merge 1 commit into
245516766 wants to merge 1 commit into
Conversation
propagateCubeUpstreamForOp (triggered by handleFillInScfIf) re-coloured ExtractedLoadStore-related ops and ops inside a nested linalg region as CUBE because the three skip predicates (arith on tensors, isExtractedLoadStoreRelated, inside nested linalg region) only lived inline inside propagateCubeUpstream. Extract the predicates into OpClassifierPass::shouldSkipCubeUpstream and call it from both BFS paths so they stay consistent. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
🔍 OpenCodeReview found 1 issue(s) in this PR.
|
Comment on lines
+927
to
+929
| bool OpClassifierPass::shouldSkipCubeUpstream(Operation *op) { | ||
| // arith dialect ops with tensor results are vector compute, not CUBE. | ||
| if (isa<arith::ArithDialect>(op->getDialect())) { |
Contributor
There was a problem hiding this comment.
[maintainability · low]
Missing null check for op parameter. The function immediately dereferences op via op->getDialect() without checking for null. While all current callers (propagateCubeUpstream and propagateCubeUpstreamForOp) guarantee non-null before calling this function, adding a defensive null check at the top would make the function more robust against future misuse and consistent with isExtractedLoadStoreRelated (which has if (!op) return false;) and isInsideNestedLinalgRegion (which guards with op ? ...).
Suggestion:
Suggested change
| bool OpClassifierPass::shouldSkipCubeUpstream(Operation *op) { | |
| // arith dialect ops with tensor results are vector compute, not CUBE. | |
| if (isa<arith::ArithDialect>(op->getDialect())) { | |
| bool OpClassifierPass::shouldSkipCubeUpstream(Operation *op) { | |
| if (!op) | |
| return false; | |
| // arith dialect ops with tensor results are vector compute, not CUBE. | |
| if (isa<arith::ArithDialect>(op->getDialect())) { |
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.
propagateCubeUpstreamForOp (triggered by handleFillInScfIf) re-coloured ExtractedLoadStore-related ops and ops inside a nested linalg region as CUBE because the three skip predicates (arith on tensors, isExtractedLoadStoreRelated, inside nested linalg region) only lived inline inside propagateCubeUpstream.
Extract the predicates into OpClassifierPass::shouldSkipCubeUpstream and call it from both BFS paths so they stay consistent.
New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD.Select one of the following.
/testforlittests/unittestfor C++ tests/python/testfor end-to-end testsFILL THIS IN.Select one of the following.
littests.littests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)