Reset derived data portably with NVFORTRAN#394
Open
krystophny wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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.
Summary
default-initialized object;
The prior constructors omit allocatable components that do not have default
initializers. GFortran accepts that form, while NVFORTRAN rejects it with
NVFORTRAN-F-0155. The replacement is compiler-portable and was also verifiedwith a focused NVFORTRAN allocation/reset probe.
Verification
fo check: build 227 modules; all tests passed in 48.4 sfo fmt --checkon both changed files: passfo lint: zero unused imports; existing 472-warning baselinegit diff --check: pass