-
Notifications
You must be signed in to change notification settings - Fork 143
Properly guard usage of openmp function calls #1435
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
Properly guard usage of openmp function calls #1435
Conversation
divyegala
left a comment
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.
We could refactor the functions a bit
divyegala
left a comment
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.
Related to previous comment
divyegala
left a comment
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.
Thanks! Looks great.
|
/merge |
833299f
into
rapidsai:branch-25.12
Proper support to disable OpenMP also requires that any calls to functions like `omp_get_max_threads` need to be guarded by a `_OPENMP` check. This is done by adding openmp wrapper functions into `cuvs/core` that properly handle the `_OPENMP` guards and behave as required when OpenMP is disabled. Required to fix rapidsai#1322 Authors: - Robert Maynard (https://github.com/robertmaynard) Approvers: - Divye Gala (https://github.com/divyegala) URL: rapidsai#1435
Proper support to disable OpenMP also requires that any calls to functions like
omp_get_max_threadsneed to be guarded by a_OPENMPcheck.This is done by adding openmp wrapper functions into
cuvs/corethat properly handle the_OPENMPguards and behave as required when OpenMP is disabled.Required to fix #1322