Use llvm.dbg.value instead of llvm.dbg.declare for SSA values
#23
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
Also insert the debug instrinsic just after the instruction that defines it. Technically these are not addresses in memory, so it's important to use `dbg.value` instead of `dbg.declare`. Without this change, almost none of the local SSA values are available in gdb (it might be just the arguments that are) but with it I can very often print the arguments of the instruction execution is halted on.
Contributor
Author
|
This doesn't seem to work for PHINodes for some reason (they don't even show up in |
There seems to be a bug upstream that drops debuginfo for PHINodes if they use a scope that is not used otherwise, so workaround this by using the Subprogram scope instead.
vaivaswatha
approved these changes
Dec 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Technically these are not addresses in memory, so it's important to use
dbg.valueinstead ofdbg.declareAlso insert the debug instrinsic just after the instruction that defines it.
Without this change, almost none of the local SSA values are available in gdb (it might be just the arguments that are) but with it I can very often print the arguments of the instruction execution is halted on:
