-
Notifications
You must be signed in to change notification settings - Fork 60
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
rocm: add reason for disabled component #219
base: master
Are you sure you want to change the base?
Conversation
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.
I personally would add a format specifier to snprintf
, but I don't believe it is actually necessary in this case or beneficial since we are providing the error message.
The rest of the file seems to follow suit with no format specifier when we directly provide the error message as well.
6dd235b
to
6dc29ca
Compare
@@ -225,7 +225,6 @@ rocm_init_private(void) | |||
fn_exit: | |||
_rocm_vector.cmp_info.initialized = 1; | |||
_rocm_vector.cmp_info.disabled = papi_errno; | |||
strcpy(_rocm_vector.cmp_info.disabled_reason, ""); |
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.
Why remove this line?
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.
This line was overwriting the error message with an empty string; I am not sure why it was here.
Previously, in the absence of a ROCm device, the rocm component did not set the string containing the reason that the component was disabled. These changes have been tested with ROCm 6.3.1 on Frontier.
6dc29ca
to
6e1a74f
Compare
Pull Request Description
Previously, in the absence of a ROCm device, the rocm component did not set the string containing the reason that the component was disabled. This corresponds to Issue #220.
These changes have been tested with ROCm 6.3.1 on Frontier.
Author Checklist
Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
Commits are self contained and only do one thing
Commits have a header of the form:
module: short description
Commits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
The PR needs to pass all the tests