-
Notifications
You must be signed in to change notification settings - Fork 57
Improve debug info for kernel arguments #242
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -290,7 +290,16 @@ def get_ufunc_info(self, ufunc_key): | |
|
|
||
|
|
||
| class CUDACallConv(MinimalCallConv): | ||
| pass | ||
| def decorate_function(self, fn, args, fe_argtypes, noalias=False): | ||
| """ | ||
| Set names and attributes of function arguments. | ||
| """ | ||
| assert not noalias | ||
| arginfo = self._get_arg_packer(fe_argtypes) | ||
| # Do not prefix "arg." on argument name, so that nvvm compiler | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that it's OK not to prefix |
||
| # can track debug info of argument more accurately | ||
| arginfo.assign_names(self.get_arguments(fn), args) | ||
| fn.args[0].name = ".ret" | ||
|
|
||
|
|
||
| class CUDACABICallConv(BaseCallConv): | ||
|
|
||
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
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.
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.
Does omitting the replacement of
.with$compared to the original implementation not cause issues for GDB? I note the comment in the original version:I thought that a dot in a name might be problematic for it? (c.f. the same syntax for traversing the members of a struct or union)
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.
That
.versioned name used to be written to the metadata node as the value of 'name' of DILocalVariable. But currently the.versioned variable nodes are merged to the unversioned / user symbol named metadata node. Therefore, they are no longer to be present in DWARF entry.And when represented as member of a struct or union, their names in the metadata are also unversioned names with corresponding types, so there won't be issues omitting this original replacement.
In short, neither
.nor$will show up in debugger.