Charm++ parallel programming system

[Evan Ramos <evan AT hpccharm.com>]

Hi Jozsef,

Thanks for the detailed information. Nothing jumps out at me as the
source of the issue, but I do have some ideas to try:

Is `-c++ /usr/bin/c++` necessary on the link line?
What happens if the two uses of c++ are changed to g++?
What happens if the compile command is passed to charmc instead of
c++/g++ directly?
Does -std=gnu++11 vs -std=c++11 make a difference?

--
Evan A. Ramos
Software Engineer
Charmworks, Inc.


On Thu, May 3, 2018 at 10:03 AM, Jozsef Bakosi 
<jbakosi AT lanl.gov>
 wrote:
> Hi Evan,
>
> Using the same setup as before, the simplearrayhello example runs fine, so 
> it
> must be something on my end. I build Charm++ on top of openmpi (2.0.2) with
>
> build charm++ mpi-linux-x86_64 --build-shared
>
> Do you want to look at the config.log, charmconfig.out or something else?
>
> Also, I completely stripped down one of the executables I build to a bare
> minimum of a mainchare whose constructor simply exits with CkExit(), i.e., 
> this
> is even simpler than simplearrayhello, and the problem persists.
>
> Here are a full compile and link lines in the hope of you might be able to 
> spot
> something unusual.
>
> MeshConv.C:
> ======================
> #include "meshconv.decl.h"
> CProxy_Main mainProxy;
> class Main : public CBase_Main {
>   public:
>     Main( CkArgMsg* msg ) {
>       delete msg;
>       mainProxy = thisProxy;
>       CkExit();
>     }
> };
>
> #include "NoWarning/meshconv.def.h"
> ======================
>
> meshconv.ci:
> ======================
> mainmodule meshconv {
>   readonly CProxy_Main mainProxy;
>   mainchare Main {
>     entry Main( CkArgMsg* msg );
>   }
> }
> ======================
>
> compile line for MeshConv.C:
>
> /usr/bin/c++   -DQUINOA_CONFIG_MPI_ENABLED -I/home/jbakosi/code/quinoa/src 
> -I/home/jbakosi/code/quinoa/src/Base 
> -I/home/jbakosi/code/quinoa/src/Control 
> -I/home/jbakosi/code/quinoa/src/DiffEq -I/home/jbakosi/code/quinoa/src/PDE 
> -I/home/jbakosi/code/quinoa/src/Walker 
> -I/home/jbakosi/code/quinoa/src/Inciter 
> -I/home/jbakosi/code/quinoa/src/LinSys 
> -I/home/jbakosi/code/quinoa/src/LoadBalance 
> -I/home/jbakosi/code/quinoa/src/IO -I/home/jbakosi/code/quinoa/src/Main 
> -I/home/jbakosi/code/quinoa/src/Mesh -I/home/jbakosi/code/quinoa/src/RNG 
> -I/home/jbakosi/code/quinoa/src/RNGTest 
> -I/home/jbakosi/code/quinoa/src/Statistics 
> -I/home/jbakosi/code/quinoa/src/UnitTest 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
>  
> -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
>  -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/hdf5/openmpi 
> -I/usr/include/hypre -I/usr/include/pstreams 
> -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/include 
> -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/include/tut 
> -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/include/pegtl/include/tao
>  -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/include/Random123 
> -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/lib/cmake/SEACASExodus/../../../include
>  -I/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/charm/include -IRNGTest 
> -ILoadBalance -IMain -IWalker -IInciter -IUnitTest -ILinSys -IIO 
> -fdiagnostics-color -Wall -Wextra -pedantic -pedantic-errors -Wcast-align 
> -Wcast-qual -Wdisabled-optimization -Wfloat-equal -Wformat=2 
> -Wformat-nonliteral -Wformat-security -Wformat-y2k -Wimport -Winit-self 
> -Winvalid-pch -Wmissing-field-initializers -Wmissing-format-attribute 
> -Wmissing-noreturn -Wpacked -Wpointer-arith -Wredundant-decls -Wshadow 
> -Wstack-protector -Wstrict-aliasing=2 -Wunreachable-code -Wunused 
> -Wunused-parameter -Wvariadic-macros -Wwrite-strings -Wno-sign-compare 
> -Wno-unused-function -Wno-stack-protector -Wno-expansion-to-defined 
> -Wno-int-in-bool-context -g   -D BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS -D 
> BOOST_MPL_LIMIT_METAFUNCTION_ARITY=20 -std=gnu++11 -MD -MT 
> Main/CMakeFiles/meshconv.dir/MeshConv.C.o -MF 
> Main/CMakeFiles/meshconv.dir/MeshConv.C.o.d -o 
> Main/CMakeFiles/meshconv.dir/MeshConv.C.o -c 
> /home/jbakosi/code/quinoa/src/Main/MeshConv.C
>
> link line:
> /home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/charm/bin/charmc -c++ 
> /usr/bin/c++  Main/CMakeFiles/meshconv.dir/MeshConvDriver.C.o 
> Main/CMakeFiles/meshconv.dir/MeshConv.C.o  -o Main/meshconv  
> -Wl,-rpath,/home/jbakosi/code/quinoa/build/gnu/IO:/home/jbakosi/code/quinoa/build/gnu/Mesh:/home/jbakosi/code/quinoa/build/gnu/Control:/home/jbakosi/code/quinoa/build/gnu/Base:/home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/lib:/usr/lib/x86_64-linux-gnu/hdf5/openmpi:
>  IO/libquinoa_meshio.so Mesh/libquinoa_mesh.so 
> Control/libquinoa_meshconvcontrol.so Base/libquinoa_base.so -lpugixml 
> /home/jbakosi/code/quinoa-tpl/install/gnu-x86_64/lib/libexodus.so.12.10.
> =======
>
> I'm puzzled.
> Jozsef
>
> On 05.02.2018 14:51, Evan Ramos wrote:
>> Hi Jozsef,
>>
>> Thanks for the info. I tested with the latest in Charm's git on Debian
>> with comparable toolchain versions and was unable to reproduce the
>> issue. Do you experience it with any of Charm's example programs?
>> Additionally, what is your Charm++ build invocation? The machine layer
>> you're using and any settings you're toggling could have an effect.
>>
>> --
>> Evan A. Ramos
>> Software Engineer
>> Charmworks, Inc.