Eric Mikida

@evan-charmworks do you have any insight on this?

Yes, I should have this ready for 6.11.

Still in progress, but I put it here to get input from @nitbhat since the primary thing it affects is some ZC stuff. The main question I have is w.r.t....

Ok, so I can't comment on unchanged files, but this function is where most of my questions lie. 1. Why is ckJustMigrated called here? And on all chares? 2. The...

The `-no-use-new-std` (and probably the `-use-new-std` arguments to build seem to be ignored. I'm working on a project that uses a std later than c++11 but when I build charm...

For this particular build I'm using `mpicc`, with `gcc version 8.4.0 (Ubuntu 8.4.0-1ubuntu1~18.04)` under the hood. I tried to reproduce what you did above but with the MPI builds, and...

Oh, and forgot to mention, even when using `./buildold` to build charm with `-use-new-std`, the `-std=c++11` still doesn't show up. So in all cases I've tried the `-use-new-std`/`-no-use-new-std` has no...

Tried `./build charm++ mpi-linux-x86_64 --build-shared -j8 -std=gnu++17` But the -verbose output is: `charmc: Executing mpicxx -fPIC -DCMK_GFORTRAN -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -I../../../bin/../include -D__CHARMC__=1 -U_FORTIFY_SOURCE -fno-stack-protector -fno-lifetime-dse -std=c++11 -c hello.C -o hello.o` For...

On a side note, maybe `(-no)-use-new-std` should be removed if they don't have any function. Or maybe they should be converted to an option that just allows you to explicitly...

`../../../bin/charmc -c hello.C -c++-option -std=gnu++17 -verbose` `charmc: Executing /home/epmikida/Programming/flecsi_devel/spack/opt/spack/linux-ubuntu18.04-skylake/gcc-8.3.0/openmpi-3.1.6-uvzp5gldea6cyniij3747hhzujzpvrcs/bin/mpic++ -DCMK_GFORTRAN -DMPICH_SKIP_MPICXX -DOMPI_SKIP_MPICXX -I../../../bin/../include -D__CHARMC__=1 -U_FORTIFY_SOURCE -fno-stack-protector -fno-lifetime-dse -std=c++11 -c hello.C -o hello.o` Does not seem to work. I don't know...