correctly pass down optimization flags in CP2K easyblock #1293
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently discovered that the optimisation flags that EasyBuild wants to use are not being passed down properly, only the
optarchflag controlling the processor architecture to optimise for (e.g.-xHostor--march=native) was.This is probably for historical reasons, but I consider this a bug now.
The main impact is that compiler options related to floating-point correctness, like
-fp-model source, are not being passed down, which may (significantly) impact accuracy of the obtained results.This change has made a big difference in the number of failing tests, see also the discussion in #1174.