-
Notifications
You must be signed in to change notification settings - Fork 5
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
OpenMP 5 fixes #25
OpenMP 5 fixes #25
Conversation
3d-runRelevant configuration parameters full file:
6d-runRelevant configuration parameters full file:
|
@MatthieuSchaller I don't have an environment with compile-time OpenMP 5.0 at hand, so if you could give these a try would be great, thanks! |
I am now on c7ea1c73e67e7f7fdfce0f035bc06dda50ca6672 for NBodyLib and b5e1a8c for VR. The messages still appear. |
@MatthieuSchaller the NBodylib commit seems the correct one. Could you run the For reference, I am using the new |
Actually you can also simply set the |
In my system, this gives me:
Note the difference between the compile-time version (201511) and the runtime version (201611). This difference is known to cause confusion, so we're not alone. |
3d-runRelevant configuration parameters full file:
6d-runRelevant configuration parameters full file:
|
Quite verbose, but kept everything in case it helps:
|
I just checked the OpenMP version that corresponds to On the one hand, the fact that Intel's compiler and OpenMP library report |
This information might be useful in the future. Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>
@MatthieuSchaller I just pushed the latest changes to require only OpenMP 3.0 to choose the new functions, could you give them a try? |
These fixes are meant to suppress deprecation warnings stemming from the use of omp_set/get_nested reported in #22. Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>
When the stf executable is run, it immediately exists if the software was compiled to support integration with swift. This fast failure however prevents the executable from showing some important information that can be useful for debugging problems like #23. Moving the fast exit only a couple of lines down allows for these informational messages to be printed before the program exits. Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>
3d-runRelevant configuration parameters full file:
6d-runRelevant configuration parameters full file:
|
3d-runRelevant configuration parameters full file:
6d-runRelevant configuration parameters full file:
|
No more messages in this latest version. |
These are fixes to suppress warnings due to VR using
omp_{get,set}_nested
, which is deprecated in OpenMP 5. The fixes are mostly in NBodylib, which checks the compile-time OpenMP version (there's no way to check the runtime version) and decides whether to use the old functions, or the newer alternatives.I took the chance of cleaning a bit the code around these function calls, trying to reduce duplication and mental load.