Logo AND Algorithmique Numérique Distribuée

Public GIT Repository
Reimplement s4u::Barrier natively, and make them visible from MC
authorMartin Quinson <martin.quinson@ens-rennes.fr>
Fri, 4 Mar 2022 21:03:19 +0000 (22:03 +0100)
committerMartin Quinson <martin.quinson@ens-rennes.fr>
Fri, 4 Mar 2022 23:10:15 +0000 (00:10 +0100)
commit97e476dc536bfd9fada85509d1c1f93714d46a10
tree96f08526106778e836da3f59fe4b078fed253c0d
parente4339afd9b4ae5f3558a0348f24b0022db3501d5
Reimplement s4u::Barrier natively, and make them visible from MC

It comes with a DPOR dependency computation and a s4u hijacked test.

The ordering of some simcalls changed in SMPI, as there now much less
of them when using barriers. This impacts in particular the order in
which PID are given in the gh-139 test. Adding a link here for reference:
https://github.com/simgrid/simgrid/issues/139

MSG_barrier_destroy() cannot take a const barrier anymore, but how was
it possible in the first place?
27 files changed:
ChangeLog
MANIFEST.in
docs/source/Release_Notes.rst
examples/cpp/CMakeLists.txt
examples/cpp/synchro-barrier/s4u-mc-synchro-barrier.tesh [new file with mode: 0644]
examples/cpp/synchro-barrier/s4u-synchro-barrier.cpp
examples/cpp/synchro-barrier/s4u-synchro-barrier.tesh
include/simgrid/barrier.h
include/simgrid/forward.h
include/simgrid/msg.h
include/simgrid/s4u/Barrier.hpp
src/kernel/activity/BarrierImpl.cpp [new file with mode: 0644]
src/kernel/activity/BarrierImpl.hpp [new file with mode: 0644]
src/kernel/actor/SynchroObserver.cpp
src/kernel/actor/SynchroObserver.hpp
src/mc/remote/AppSide.cpp
src/mc/transition/Transition.cpp
src/mc/transition/Transition.hpp
src/mc/transition/TransitionSynchro.cpp
src/mc/transition/TransitionSynchro.hpp
src/msg/msg_legacy.cpp
src/s4u/s4u_Barrier.cpp
src/smpi/include/smpi_win.hpp
src/smpi/internals/smpi_deployment.cpp
src/smpi/mpi/smpi_win.cpp
teshsuite/smpi/gh-139/gh-139.tesh
tools/cmake/DefinePackages.cmake