Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change some associate block to fix GNU crash #1245

Merged
merged 2 commits into from
Dec 18, 2021

Conversation

weiyuan-jiang
Copy link
Contributor

@weiyuan-jiang weiyuan-jiang commented Dec 18, 2021

gfortran crashes at blocks that associate an allocated string. Those blocks are changed to fix the crash. There are some minor cleanups in this PR too.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Trivial change (affects only documentation or cleanup)

Checklist:

  • I have tested this change with a run of GEOSgcm (if non-trivial)
  • I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
  • I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

@weiyuan-jiang weiyuan-jiang added 0 Diff The changes in this pull request have verified to be zero-diff with the target branch. bugfix labels Dec 18, 2021
@weiyuan-jiang weiyuan-jiang requested a review from a team as a code owner December 18, 2021 00:44
Copy link
Contributor

@atrayano atrayano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The variable 'extension' has not been initialized yet when used in the __ASSERT at line 4852

@atrayano atrayano merged commit c114949 into develop Dec 18, 2021
@atrayano atrayano deleted the bugfix/wjiang/gnu_associate branch December 18, 2021 21:10
@mathomp4
Copy link
Member

Note: I'm going to tag @tclune here. I think he is more a fan of snake case (parent_gc) than camel case (parentGC). So he might be doing a bit of a posteriori work on this...

@weiyuan-jiang
Copy link
Contributor Author

Here parentGC is just a little bit more consistent among several related subroutines. I agree the snake style makes more sense in Fortran in general.

@tclune
Copy link
Collaborator

tclune commented Jan 3, 2022

Already done, but we often have to preserve existing oddities with argument names for backwards compatibility. Probably not even worth risking for MAPL 3 unless someone is very confident ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 Diff The changes in this pull request have verified to be zero-diff with the target branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants