-
Notifications
You must be signed in to change notification settings - Fork 109
[Pass] Support lift constants to initializers pass #2160
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
justinchuby
merged 16 commits into
microsoft:main
from
titaiwangms:titaiwang/add_constant_to_initilizer_pass
Apr 10, 2025
Merged
Changes from 1 commit
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
c662194
support lift constants to initializers pass
titaiwangms c59af87
resolve conflict
titaiwangms c0ea8e6
lint
titaiwangms 7db9be0
update name authority
titaiwangms c007277
Merge branch 'main' into titaiwang/add_constant_to_initilizer_pass
titaiwangms 1956c7f
update
titaiwangms 0ba7025
add constant attribute variations
titaiwangms c830972
add tests
titaiwangms a285ceb
add support to subgraph
titaiwangms 3b15f45
Merge branch 'main' into titaiwang/add_constant_to_initilizer_pass
titaiwangms 22df674
add new tests
titaiwangms 2c87912
Merge branch 'main' into titaiwang/add_constant_to_initilizer_pass
titaiwangms 82c4016
address reviews
titaiwangms a2e9d2a
assert to self.assert
titaiwangms 0a731e6
Merge branch 'main' into titaiwang/add_constant_to_initilizer_pass
titaiwangms e648167
Update onnxscript/ir/passes/common/constant_manipulation_test.py
titaiwangms 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
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.
@justinchuby does this make sense? I think there should not be any ir.Function node coming out from recursive iterator?
Uh oh!
There was an error while loading. Please reload this page.
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.
Does make sense. Thanks! The reason why it was annotated with graph | function is that the “owning graph” can be a function when the node is part of a function. Maybe there are better ways to do it 🤔
Uh oh!
There was an error while loading. Please reload this page.
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.
(Unrelated to this PR): Isn't a Function object a wrapper around a Graph object? Does node.graph not return that graph object even in the case of function nodes?
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.
Technically the graph in a function is private and not used directly. It is currently an implementation detail
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.
sorry I was wrong. It is pointed to a graph when we call
function.append, but it is not when we call ir.Node(graph=function). I need to figure out how to reconcile this. Suggestions appreciated. #2181There 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.
#2183