[6.0] [DebugInfo] Return complete variable info from getVarInfo by default #73652
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
The scope of a store has to be the variable's scope. The type should be set to the element's type, and only if not already set. The variable's location should be set. (cherry picked from commit 7c9676e)
We should not dereference the file position if this SILLocation is not a position. If it's a pointer, we compare the pointers. (cherry picked from commit bc3bf84)
(cherry picked from commit 784034f)
We do keep the fragment part of the expression as it is important to identify fragments separately. A variable with less fragments should be considered a superset of variables with more fragments, but that would require to change a lot of code. (cherry picked from commit b293099)
(cherry picked from commit 9c78317)
The type of the new variable should be opened too. If the variable has an expression modifying the type, it cannot be rewritten and is dropped. (cherry picked from commit 5f2926c)
(cherry picked from commit ac865eb)
getVarInfo() now always returns a variable with a location and scope. To opt out of this change, getVarInfo(false) returns an incomplete variable. This can be used to work around bugs, but should only really be used for printing. The complete var info will also contain the type, except for debug_values, as its type depends on another instruction, which may be inconsistent if called mid-pass. All locations in debug variables are now also stripped of flags, to avoid issues when comparing or hashing debug variables. (cherry picked from commit 0be63d0)
(cherry picked from commit 9984d1d)
|
@swift-ci test |
adrian-prantl
approved these changes
May 15, 2024
rdar://128091794 (cherry picked from commit f704a0c)
|
@swift-ci test |
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.
Uh oh!
There was an error while loading. Please reload this page.