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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Transform] Modify FuseTIR pass to propagate buffer attributes #17075
[Transform] Modify FuseTIR pass to propagate buffer attributes #17075
Changes from all commits
bac24e1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a test case for incompatible usage of a single Relax var? As currently written, we could have a single Relax variable that is used in two separate
R.call_tir
statements, where the function being called imposes different restrictions on it. For example, ifx
were used incls.add1
, which requiresaxis_separators=[1]
, andcls.add2
, which requiresaxis_separators=[]
. We should be able to identify this case and raise an error when it occurs.(Ideally, that should never happen, but this would be the last point at which we'd have enough information to catch this failure mode at compile-time.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added the test case to check possible inconsistencies.