Automatic Enumeration of NVTX Range IDs #616
Merged
Conversation
This file contains 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
|
/blossom-ci |
cliffburdick
approved these changes
May 10, 2024
|
/blossom-ci |
|
/blossom-ci |
1 similar comment
|
/blossom-ci |
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.
Enable an automatic enumeration capability to free users from needing to unique ID each range.
Overloads the MATX_NVTX_RANGE to work with any number of parameters.
This PR also addresses an issue where all ranges created by the MATX_NVTX_RANGE macro were limited to the scope they were created in; now the NVTX range will persist until ended by the user.
Changed the default log level to USER from internal, to not require the user to manually set the log level each time.