Charm++ parallel programming system

["Van Der Wijngaart, Rob F" <rob.f.van.der.wijngaart AT intel.com>]

Thanks, Phil. I could track the following dependencies: conv-mach.sh is called by conv-config.sh, which is called by special.sh, which is called by the Makefile in src/scripts/Makefile. As far as I can tell, cc-mpicxx.sh is not called by anything. I may be able to reverse engineer the scripts, but could I ask you to give me a pointer how to tweak the build line so I can use the Intel compilers? I assume someone else has also tried to do that in the past. Thanks!

 

Rob

 

From: unmobile AT gmail.com [mailto:unmobile AT gmail.com] On Behalf Of Phil Miller
Sent: Friday, September 19, 2014 2:21 PM
To: Van Der Wijngaart, Rob F
Cc: Nikhil Jain; charm AT cs.illinois.edu
Subject: Re: [charm] Using icc/icpc with Charm

 

Have a look at src/arch/mpi-linux-x86_64/conv-mach.sh and src/arch/mpi-linux-x86_64/cc-mpicxx.sh. Between those two, you should be able to tweak the commands and arguments used by charmc to generate the overall backend compiler command line.

 

On Fri, Sep 19, 2014 at 4:17 PM, Van Der Wijngaart, Rob F <rob.f.van.der.wijngaart AT intel.com> wrote:

Hi Nikhil,

Sadly, this did not work, even though mpiicpc is indeed installed and in my path. The problem is, of course, that I do not issue the compilation commands myself, charmc does, so I cannot influence how mpiicpc is invoked. Overall, the charmc interface if fairly obscuring. I did not know I was using g++ behind the scenes, until I specified some compiler flags in my makefile that are Intel compiler specific.

Rob

../../../bin/charmc -O3 -fno-alias  jacobi2d.ci
../../../bin/charmc -O3 -fno-alias -c jacobi2d.C
g++: error: unrecognized command line option "-fno-alias"

-----Original Message-----
From: nikhil.life AT gmail.com [mailto:nikhil.life AT gmail.com] On Behalf Of Nikhil Jain
Sent: Thursday, September 18, 2014 5:11 PM
To: Van Der Wijngaart, Rob F
Cc: Phil Miller (mille121 AT illinois.edu); charm AT cs.illinois.edu
Subject: Re: [charm] Using icc/icpc with Charm

Jumping in to suggest what I think could be done.

Do you have an mpi* wrappers that default to Intel C/C++ compilers? If
yes, the following can be done:

MPICXX=mpiicpc CXX=icpc ./build charm++  mpi-linux-x86_64 mpicxx ifort
smp --with-production -j8 -DMPICH_IGNORE_CXX_SEEK -DMPICH_SKIP_MPICXX

assuming the mpi* wrapper that default to ICC is named mpiicpc, else
it can be replaced with the right name for you. You can similarly also
prefix MPICC= and CC= to let Charm pick the right names for C code.

--Nikhil

On Thu, Sep 18, 2014 at 6:28 PM, Van Der Wijngaart, Rob F
<rob.f.van.der.wijngaart AT intel.com> wrote:
> Hi Phil,
>
>
>
> Do you know how I should modify my build line to be able to use the Intel
> C/C++ compilers, in addition to mpicxx? This is what I have today:
>
> ./build charm++ mpi-linux-x86_64 ifort mpicxx smp -j8
> -DMPICH_IGNORE_CXX_SEEK -DMPICH_SKIP_MPICXX
>
>
>
> Thanks!
>
>
>
> Rob
>
>
> _______________________________________________
> charm mailing list
> charm AT cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/charm
>



--
Nikhil Jain, nikhil.jain AT acm.org, http://charm.cs.uiuc.edu/people/nikhil
Doctoral Candidate @ CS, UIUC