LLVM Memory Sanitizer issues for eCLM-PDAF #48
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
78ac0ad to
f9386c3
Compare
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.
For eCLM-PDAF, specifying the debug compiler option
-check allhas lead to runtime errors related to the LLVM Memory Sanitizer (MSAN).For now, this branch removing the compiler option
-check allis provided.This will be investigated further in the future.
A more fine-grained analysis of the compiler options summarized under
-check allcould be needed. In particular the LLVM Memory Sanitizer (MSAN) is invoked by-check uninit.See https://www.intel.com/content/www/us/en/docs/fortran-compiler/developer-guide-reference/2025-0/check.html