-
Notifications
You must be signed in to change notification settings - Fork 561
Migrate to upstream OpKind #3398
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
|
@wonjoolee95 Could you add a more detail description? Like which class you are migrating to, what's the difference between existing class and upstream etc |
@JackCaoG Sure thing, meant to update it earlier this morning. This is more of an attempt to make the original PR #3385 smaller. Added in some info to the PR summary on top. |
JackCaoG
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.
Thanks! Could you fix the conflict?
|
Fixed some merge conflicts. Will merge as CI tests pass. |
4df8777 to
cdd2631
Compare
Migrates existing
torch_xla::ir::OpKindtotorch::lazy::OpKind, which is required to migrateNode,Value, andOutputclasses. This PR only does simple replacement (no inheritance, logic change, etc), since the existingtorch_xla::ir::OpKindand the upstreamtorch:lazy::OpKindare the same. This PR replaces all the calls and initializations totorch::lazy::OpKind.Initially was part of #3385, separated into the new PR to make the original PR bit smaller and easier to review.