-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[JIT] Write out SourceRanges on save() #22179
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
Add token stack wire up stack i fucked up something salvageable [JIT] with debug prints no more debug prints pickle stuff
[JIT] Preserve SourceRanges across serialization Add token stack wire up stack i fucked up something salvageable [JIT] with debug prints no more debug prints pickle stuff gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
[JIT] Preserve SourceRanges across serialization Add token stack wire up stack i fucked up something salvageable [JIT] with debug prints no more debug prints pickle stuff gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
[JIT] Preserve SourceRanges across serialization Add token stack wire up stack i fucked up something salvageable [JIT] with debug prints no more debug prints pickle stuff gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
[JIT] Preserve SourceRanges across serialization Add token stack wire up stack i fucked up something salvageable [JIT] with debug prints no more debug prints pickle stuff gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
zdevito
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.
This looks pretty good. I have a couple comments about encapsulating the tagged streams, and making sure we do not create tons of small strings that should be addressed.
[JIT] Preserve SourceRanges across serialization gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
zdevito
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.
This is getting close -- I think there are still some bugs distinguishing places where variables are used and where they are defined. We should not be switching the source range when a variable is used. I also have some concerns about how big the debug information is because the source ranges are not being de-duplicated. There are a lot of really small strings " = " That are 3 bytes but will turn into >32 bytes of serialized data in the current format.
[JIT] Preserve SourceRanges across serialization gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
[JIT] Preserve SourceRanges across serialization gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
[JIT] Preserve SourceRanges across serialization gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
zdevito
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.
ngnt
[JIT] Preserve SourceRanges across serialization gh-metadata: pytorch pytorch 22179 gh/jamesr66a/8/head
|
@jamesr66a merged this pull request in 2c2a913. |
Summary: Pull Request resolved: pytorch#22179 ghimport-source-id: 9879551 Test Plan: Imported from OSS Differential Revision: D15981423 Pulled By: jamesr66a fbshipit-source-id: a2506f5a2f05916b6e8226841b0229110e758671
Stack from ghstack:
Differential Revision: D15981423