slizzered
commented
9 years ago There are some unfixed warnings in the pulled GrayBat subtree, I think.
In file included from /home/eckert62/haseongpu/src/calc_phi_ase_graybat.cc:35:0:
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp: In constructor ‘graybat::communicationPolicy::BMPI::Event::Event(boost::mpi::request)’:
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:160:16: warning: ‘graybat::communicationPolicy::BMPI::Event::request’ will be initialized after [-Wreorder]
mpi::request request;
^
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:159:28: warning: ‘const bool graybat::communicationPolicy::BMPI::Event::async’ [-Wreorder]
const bool async;
^
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:108:3: warning: when initialized here [-Wreorder]
Event(mpi::request request) : request(request), async(true){
^
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp: In constructor ‘graybat::communicationPolicy::BMPI::Event::Event(boost::mpi::status)’:
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:161:30: warning: ‘graybat::communicationPolicy::BMPI::Event::status’ will be initialized after [-Wreorder]
mpi::status status;
^
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:159:28: warning: ‘const bool graybat::communicationPolicy::BMPI::Event::async’ [-Wreorder]
const bool async;
^
/home/eckert62/haseongpu/include/graybat/communicationPolicy/BMPI.hpp:112:17: warning: when initialized here [-Wreorder]
Event(mpi::status status) : status(status), async(false){
^
erikzenker
Introduced GrayBat recv from any adjacent vertex, such that the first vertex that sends a msg will be served first.