-
Notifications
You must be signed in to change notification settings - Fork 76
[Triton] Use UnitAttr in tt.reshape definition
#2497
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
Conversation
Use `UnitAttr` in `tt.reshape` definition to make working with them and creating them easier. `allow_reorder` and `efficient_layout` are now `UnitAttr`, allowing dropping the additional constructor. Signed-off-by: victor-eds <[email protected]>
|
Noticed this flaw when working with the operation. Will make working with it cleaner. Worth upstreaming. |
|
Now we get the very convenient: static ReshapeOp build(/*...,*/ Type type, Value src, bool allowReorder = false, bool efficientLayout = false); |
|
Make code needed for #2266 simpler. |
FMarno
left a comment
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.
Good Idea
|
If the Intel side is happy with this, I'll push a PR upstream. This isn't blocking us, but it may make working with this op easier. |
whitneywhtsang
left a comment
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.
LGTM, let's upstream it.
|
Closing as upstream PR is up for review. |
Use
UnitAttrintt.reshapedefinition to make working with them and creating them easier.allow_reorderandefficient_layoutare nowUnitAttr, allowing dropping the additional constructor.