Workaround for Cray compiler bug involving NULL()
intrinsic
#1560
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.
Description
The Cray compiler contains a bug where the
NULL()
intrinsic fails to produce a pointer of the correct type when it is passed directly to a subroutine expecting a pointer to a derived type.This PR implements a workaround where
NULL()
is assigned to a variable which is passed to the subroutine, rather than callingNULL()
directly as a subroutine argument.How Has This Been Tested?
Builds with Cray compiler 15.0.1 on C5.
Checklist:
make distcheck
passes