Jim Edwards

@edhartnett How will using PIO like this in the FMS library work in an executable (CESM) that also has components that use PIO directly?

An important question that I think we need to answer before moving forward since both the fv3 atmosphere and the mom ocean are potential cesm components.

Yes, it also appears to happen with a C program, here is a test: ``` #include #include #include /* strcpy(), strncpy() */ #include /* getopt() */ #include /* time() localtime(),...

It seems to be an xl compiler issue. The same test using pgi is okay. (on the same machine and using the same MPI library)

HI @wkliao the IBM folks tell me that a workaround is to compile without optimization. It could be that the netcdf build was without -O and the pnetcdf c build...

Adding the flag below solves the problem. ncx.lo: LTCOMPILE += -qnoinline On Wed, Oct 24, 2018 at 8:55 AM Rafik Zurob wrote: > Our recommendation is to add -fno-strict-aliasing for...

It's a little endian On Wed, Oct 24, 2018 at 12:00 PM Wei-keng Liao wrote: > Hi @rzurob and @jedwards4b > > May I assume you are testing this on...

It works for the ibm compiler, however now when I try to use the pgi compiler on the same system I am still getting that -fno-strict-aliasing flag.

checking if C compiler is pgcc... no mpicc --version pgcc 18.7-0 linuxpower target on Linuxpower PGI Compilers and Tools Copyright (c) 2018, NVIDIA CORPORATION. All rights reserved.

I see the problem - in acinclude.m4: