Am 25.05.23 um 19:01 schrieb Steve Kargl:
On Thu, May 25, 2023 at 04:05:11PM +, Thompson, Matt (GSFC-610.1)[SCIENCE
SYSTEMS AND APPLICATIONS INC] via Fortran wrote:
Thomas,
Well, the code did not change. Period. Neither did the compiler. It was 12.3.
(We can't use GCC 13 because it seems
On Thu, May 25, 2023 at 04:05:11PM +, Thompson, Matt (GSFC-610.1)[SCIENCE
SYSTEMS AND APPLICATIONS INC] via Fortran wrote:
> Thomas,
>
> Well, the code did not change. Period. Neither did the compiler. It was 12.3.
> (We can't use GCC 13 because it seems not to like something in our advanced
Thomas,
Well, the code did not change. Period. Neither did the compiler. It was 12.3.
(We can't use GCC 13 because it seems not to like something in our advanced
Fortran code (lots of OO, submodules, string fun...)).
And I did a run with essentially all the GNU checks on (our Debug build mode)
Hi Matt,
Recently, one of the computing centers I run on updated their > OS. And in that update,
the model went from "working with GNU"
to "crashing with GNU". No code change on our side, just OS.
That sounds suspicious, and points to possible bugs in the
code.
Hmm... does the upgrade mean
All,
Recently, one of the computing centers I run on updated their OS. And in that
update, the model went from "working with GNU" to "crashing with GNU". No code
change on our side, just OS.
Some experimenting later and I found that the code did run with debugging
options, and it still ran wit
