0-size allocations for owned fields #25
Merged
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.
Throughout the IFS, we initialize 0-sized owned fields (a workaround for when a particular field is meant to be disabled). Whilst these 0-sized allocations are safe using the Fortran
ALLOCATE
statement, they cause errors inC_MALLOC
. This PR adds safety checks so that 0-sized allocs can be handled safely using FortranALLOCATE/DEALLOCATE
.We need
C_MALLOC
because there is an upper limit on registering Fortran allocated memory in page-locked memory (which is lower than the OS limit).