Pavan, That worked. Now, my second question, should I compile the entire application with mpecc or just using mpecc during the last linking step is sufficient? Specifically, I have a scenario where I am already overriding some MPI functions such as MPI_Init, MPI_Finalize, and MPI_Barrier. So, I am trying to do a two step process: Step 1: Create a relocatable binary with my intercepted MPI calls: CC -Wl,-r -o foo_r foo.cpp -nostdlib -Wl,--wrap=MPI_Init -Wl,--wrap=MPI_Finalize -Wl,--wrap=MPI_Barrier my_mpi_intercepts.o Step 2: Create the final executable by linking with MPECC $MPECC -o foo foo_r -mpilog When I do this, the generated executable does not produce any clog2 logs. -Milind On Wed, Sep 17, 2014 at 12:52 PM, Balaji, Pavan <[email protected]> wrote:
You’ll need to download the latest version.
http://www.mpich.org/static/mpe/downloads/
I’ll need to figure out the exact download tarballs and clean up the above link, but for now you can pick the latest version of MPE2.
— Pavan
On Sep 17, 2014, at 12:32 PM, Milind Chabbi <[email protected]> wrote:
Pavan,
Now, I am trying MPE2 present inside mpich2-1.4.1p1. It runs into several compilation issues (see below). Do you have any suggestions?
Can you tell me how MPE2 achieves the logging? Does it divert MPI_ calls through its own functions? On static libraries does it use linker wrapping? For a large application simply changing the last linker step to use mpecc would suffice or does it need the whole application to be recompiled with mpecc wrapper?
-------------------------------------------------------- **** Making src/wrappers ....
make --no-print-directory build_lib_bin
cc -I.. -I../../../../src/wrappers/include -I/global/homes/m/mc29/software/mpich2-1.4.1p1/src/mpe2/BUILD/include -I../../.. -I../../../../src/wrappers/../../include -c ../../../../src/wrappers/src/log_mpi_util.c
cc -I.. -I../../../../src/wrappers/include -I/global/homes/m/mc29/software/mpich2-1.4.1p1/src/mpe2/BUILD/include -I../../.. -I../../../../src/wrappers/../../include -c ../../../../src/wrappers/src/log_mpi_core.c
../../../../src/wrappers/src/log_mpi_core.c: In function 'MPI_Allgather':
../../../../src/wrappers/src/log_mpi_core.c:1550:8: error: argument 'sendbuf' doesn't match prototype
void * sendbuf;
^
In file included from ../../../../src/wrappers/src/log_mpi_core.c:10:0:
/opt/cray/mpt/6.3.1/gni/mpich2-gnu/48/include/mpi.h:945:5: error: prototype declaration
int MPI_Allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
^ --------------------------------------------------------
On Wed, Sep 17, 2014 at 6:20 AM, Balaji, Pavan <[email protected]> wrote:
Milind,
Did you try this link?
http://wiki.mpich.org/mpich/index.php/MPE_by_example
— Pavan
On Sep 17, 2014, at 12:26 AM, Milind Chabbi <[email protected]> wrote:
I am trying to gather MPI logs on CRAY XC30 (Edison machine at NERSC.) I built MPE 2-1.3 (ftp://ftp.mcs.anl.gov/pub/mpi/mpe/mpe2.tar.gz) with the following configure command:
./configure MPI_CC=cc F77=ftn MPI_F77=ftn --prefix=/XXXXX/mpe2-1.3.0-install
I compiled a simple application with the following command: /XXXX/mpe2-1.3.0-install/bin/mpecc test1.cpp -mpilog
The code compiled fine, but the execution did not generate any log files.
I am trying to generate logs files of MPI calls to view with Jumpshot on programs compiled on Cray XC30. Can you suggest the steps needed to get this working?
Thanks -Milind _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
-- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
-- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss