-
Notifications
You must be signed in to change notification settings - Fork 15.2k
[OpenMP] Fix preprocessor mismatches between include and usages of hwloc #158349
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
base: main
Are you sure you want to change the base?
Conversation
Thank you for submitting a Pull Request (PR) to the LLVM Project! This PR will be automatically labeled and the relevant teams will be notified. If you wish to, you can add reviewers by using the "Reviewers" section on this page. If this is not working for you, it is probably because you do not have write permissions for the repository. In which case you can instead tag reviewers by name in a comment by using If you have received no comments on your PR for a week, you can request a review by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate is once a week. Please remember that you are asking for valuable time from other developers. If you have further questions, they may be answered by the LLVM GitHub User Guide. You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums. |
The proposed changes are an attempt to fix the build issues on Darwin, but are currently untested since I don't work on a Mac. If someone could check whether this fixes the issue or ping people who can, that would be great:) |
I don't think it is necessary to replace all How about |
f001c80
to
a61b86e
Compare
@jprotze True, it's not strictly necessary, but the motivation was to help preventing similar issues in the future, since it is easy to overlook that I have tested it with Thanks for suggesting |
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 think KMP_INCLUDES_HWLOC
does not correctly describe what it actually means. KMP_USE_HWLOC
is to enable hwloc support in general, bearing in mind that additional conditions may disable it again. I think KMP_HWLOC_ENABLED
might be a better choice, because it then describes that a) hwloc.h
has been included, and b) that the hwloc-based affinity code is also enabled.
openmp/runtime/src/kmp_affinity.cpp
Outdated
#include "kmp_dispatch_hier.h" | ||
#endif | ||
#if KMP_USE_HWLOC | ||
#if KMP_INCLUDES_HWLOC |
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.
Several of these do not have the comment to indicate which #endif
is closing off that compilation guards. It would be great if you could add them.
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.
Done
KMP_HWLOC_ENABLED expresses whether hwloc is included *and* hwloc-based affinity is enabled.
@mjklemm I've now changed it back to use |
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.
LGTM. Thanks for making the changes!
Fix #156679
There is a mismatch between the preprocessor guards around the include of
hwloc.h
and those protecting its usages, leading to build failures on Darwin: spack/spack-packages#1212The suggested change introduces
KMP_INCLUDES_HWLOC
KMP_HWLOC_ENABLED
that reflects whether hwloc is actually used.I realize that having bothKMP_USE_HWLOC
andKMP_HWLOC_ENABLED
could be confusing, so I'm open to alternative naming suggestions.