Closed jcphill closed 7 years ago
Original date: 2017-05-26 17:17:51
OK, reproduced with ./build charm++ multicore-darwin-x86_64 --no-build-shared --enable-tracing --enable-tracing-commthread -optimize
- no need for the Intel compilers to hit this. Looking at the relevant code, and rebuilding accordingly, it's specifically --enable-tracing-commthread
The same issue arises with
./build charm++ netlrts-darwin-x86_64-smp --enable-tracing-commthread -j5 -g
cd netlrts-darwin-x86_64-smp/tests/converse/megacon
make
Original date: 2017-05-26 17:27:48
https://charm.cs.illinois.edu/gerrit/2558 https://github.com/UIUC-PPL/charm/commit/ef205bc39a5469b853c82e31cf5ed3513d13aaaa
Original issue: https://charm.cs.illinois.edu/redmine/issues/1574
One example, on Bridges:
Note that megatest (Charm++) works, as does NAMD.
The following NAMD builds have this issue, which is exactly the lrts layers with smp/multicore: Beagle-smp.log BlueGeneQ-lrts.log Bridges-MPI-smp.log Bridges-multicore.log BW-smp.log Cori-KNL-smp.log Cori-smp.log Edison-smp.log Jetson.log JYC-smp.log Linux-KNL-multicore.log Linux-x86_64-lrts-smp.log Linux-x86_64-multicore-gcc.log Linux-x86_64-multicore.log Linux-x86_64-verbs-smp.log MacOSX-x86_64.log Stampede2.log Stampede2-multicore.log Stampede-verbs-smp.log Taub-verbs-smp.log Theta.log Titan-smp.log Win64.log Win64-MPI-smp.log