Charm++ parallel programming system

[Phil Miller <mille121 AT illinois.edu>]

We have encountered numerous quirks in attempts to compile Charm++ with the Cray C++ compiler suite. Ultimately, we have a pending patch from Cray staff to clean up some incompatibilities in our code, and corresponding fixes in their compiler that will be released sometime soon.

When we can validate support for the Cray compiler, we'll be sure to make an announcement.

On Wed, Nov 30, 2016 at 11:43 AM, Jozsef Bakosi <jbakosi AT gmail.com> wrote:

Hi folks,

I have successfully built Charm++ using the Cray C++ compiler suite with the following build command:

$ build charm++ mpi-crayxc craycc --with-production

Now when I try to compile code that includes pup.h, which includes converse.h, which includes intrinsics.h, I get the error:

CC-311 crayc++: ERROR File = /opt/cray/pe/cce/8.5.4/CC/x86-4/compiler_include_base/basic/intrinsics.h, Line = 273

  An overload function cannot be distinguished by the return type alone.

  extern int64_t _popcnt32(uint32_t);

The section of converse.h in question is:

#if CMK_C_BUILTIN_IA32_XFENCE

#include <intrinsics.h>

#endif

If I comment out including intrinsics.h above, the particular error above goes away. This only happens on Crays and only with the Cray C++ compiler, but with all available cce modules, i.e., the intrinsics.h associated to all available cce versions. Interestingly, I cannot find an intrinsics.h system-wide on linux for example, so the non-existence of this header does not seem to be an issue, but on the two Cray machines I have tested this, the above system-wide header consistently gets picked up and fails to compile. I also wonder why this header is not picked up during building Charm++ itself.

What do you guys suggest fixing this problem?

Thanks,

Jozsef