Add macro for Scorep instrumentation of a user-defined code region #1784
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
d7919
previously approved these changes
Aug 13, 2019
|
Yes, I went from the quick reference here: |
|
Can |
|
Thanks @ZedThree, that is simpler - updated! |
Like with SCOREP0, this macro is defined to be null if BOUT is compiled without scorep. Also update coresponding docs.
JosephThomasParker
changed the title
|
Sorry, mission creep. The approach documented doesn't build when BOUT is configured without scorep, so I've added a macro for the region that vanishes when there's no scorep support. |
|
@d7919 - yes it works for me locally and on Archer. 🙂 |
ZedThree
reviewed
Aug 13, 2019
ZedThree
approved these changes
Aug 13, 2019
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.
Add a macro to allow scorep instrumentation of a user-defined region of code. The section of code
appears as "region name" in the Scalasca profile. AIUI, the existing
SCOREP0macro can't be used to do this, as it (very usefully) times the whole function and automatic uses the function name as its display name.