-
Notifications
You must be signed in to change notification settings - Fork 684
Arm backend: Move rescale ops out of node visitors #14584
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
2cda2ff
Arm backend: Move rescale ops out of comparison visitors
a647bc3
Arm backend: Move rescales from ABS visitor to pass
463ed4a
Arm backend: Move rescales from MAXIMUM/MINIMUM visitor to pass
17d7fb3
Merge branch 'main' into marlin-move-rescales
martinlsm d4c5afb
Merge branch 'main' into marlin-move-rescales
martinlsm 75611db
Merge branch 'pytorch:main' into marlin-move-rescales
martinlsm f21cf7f
Arm backend: Move rescales from SUB visitor to pass
0b65f38
Revert "Arm backend: Move rescales from SUB visitor to pass"
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
may be this boat has sailed already but for logical grouping perspective, I would rather keep the util call in respective ops instead of a pass.. but that's just me. Not a strong objection.
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.
@digantdesai Not sure what you mean fully. Can you elaborate a bit?
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.
Instead of inserting rescale ops in the tosa graph through this pass, I would prefer (mild preference) of keeping the way things were, i.e. an op lowering (op_.py) would inject an op when needed.
This is mainly to keep things together logically and keep the tosa graph 'sound' after each op lowering.
That said I understand the code duplication aspect, but that could be tackled with keeping these
insert rescale
as util functions.Again, not a strong objection. Stamping to unblock you, and leaving it up to you to decide.
Thanks!