Tom Clune

Same request as the other. Please change to PR onto develop branch.

@kurtsansom - do you still intend to resubmit this as a PR onto develop?

A colleague has also found a problem in the lower level gFTL layer under this new Intel compiler. Unfortunately, I don't yet have access to that version so cannot explore...

There is currently a bit of a mess in the Cmake logic across the GFE components in pFUnit. Some contributed code broke some cases that are not covered by the...

Newer versions of pFUnit require more recent versions of gFortran. That particular issue is only the first of many you will encounter when trying to use GFortran 5.x. I recommend...

To a large extent pFUnit 4.0 was just a major cleanup of 3. The new design is more extensible - e.g., pfunit is now just an extra layer/library on top...

Hmm. I did not think gcc-7 was working with pfunit even before that change. Any chance you can adapt to a more recent gcc? I can attempt a workaround next...

In the mean time, you can create your own branch that uses earlier fArgParse. The updates were mostly just to get everything up to the latest gFTL for an indirect...

@cponder - sorry about that. Forgot to commit the NVHPC.cmake file. Will do so shortly.

Sorry - did not notice that this was in the pFUnit repo. I think a number of changes are needed here and in fArgParse to use the kludged gFTL. But...