Skip to content
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

misc: Fix warnings from NVHPC compilers #7253

Open
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

raffenet
Copy link
Contributor

@raffenet raffenet commented Jan 2, 2025

Pull Request Description

Attempt to make compilation with NVHPC compilers warning clean. I'm not 100% confident in 486c2c3 or ef0474f, but hopefully testing will prove them correct.

Author Checklist

  • Provide Description
    Particularly focus on why, not what. Reference background, issues, test failures, xfail entries, etc.
  • Commits Follow Good Practice
    Commits are self-contained and do not do two things at once.
    Commit message is of the form: module: short description
    Commit message explains what's in the commit.
  • Passes All Tests
    Whitespace checker. Warnings test. Additional tests via comments.
  • Contribution Agreement
    For non-Argonne authors, check contribution agreement.
    If necessary, request an explicit comment from your companies PR approval manager.

@raffenet
Copy link
Contributor Author

raffenet commented Jan 2, 2025

test:mpich/ch4/most
test:mpich/ch4/more
test:mpich/ch3/most

@raffenet
Copy link
Contributor Author

raffenet commented Jan 2, 2025

test:mpich/ch4/most
test:mpich/ch3/most

libpmi functions return a pmi_errno, not a HYD_status. Make sure to
capture the value in the right variable type and perform the necessary
check on it.
Make sure to use unsigned long long when constructing tag bits to avoid
signed integer conversion warning.
Avoid directly using object free macros and causing a set but unused
warning on the in_use parameter.
Use an appropriate type or cast when setting variable to -1 to avoid a
sign conversion warning.
progress_state is not used when just poking the progress engine. In
fact, the progress start/end macros in ch3 are no-ops. In this case the
whole function can be reduced down to just MPID_Progress_poke(), so do
that.
These checks are not needed and lead to warnings due to set but unused
variable.
@raffenet
Copy link
Contributor Author

raffenet commented Jan 2, 2025

test:mpich/ch4/most
test:mpich/ch3/most

@raffenet
Copy link
Contributor Author

raffenet commented Jan 3, 2025

test:mpich/custom
env: MPIR_CVAR_ASYNC_PROGRESS=1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant