[Cherrypick]Serialize/Deserialize source locations for instructions (#77281) #79578
Conversation
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 commit adds support for serializing and deserializing source locations for instructions.
Contributor Author
| @swift-ci test |
Contributor Author
| @swift-ci test please |
Contributor
| I don't think there is a compelling reason to cherry-pick this to |
adrian-prantl requested changes Feb 24, 2025
Contributor
adrian-prantl left a comment
adrian-prantl left a comment There was a problem hiding this comment.
I don't think there's a compelling reason to cherry-pick this to 6.1?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Explanation:
This commit adds support for serializing and deserializing source locations for instructions.
Scope:
This is gated behind a flag currently so does not have any effect until enablement.
Original PR:
#77281
Risk:
Low since this does not include enablement of the flag
Testing:
Testing has been done locally while building with the flag enabled, and I have also added tests
Reviewers:
adrian-prantl