June 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Error while building NAS benchmarks
by "Antonio J. Peña" 02 Jun '15

02 Jun '15

Sorry, this mailing list is specifically intended to discuss issues with MPICH itself. For issues with its derivatives (such as Intel MPI), please seek assistance in their own forums, or alternatively, in general programming sites such as stackoverflow.com Best, Antonio On 06/02/2015 02:35 PM, koko jumbo wrote: > I am trying to build NAS benchmarks using Intel MPI and below is the > makefile that I am using. > > * #---------------------------------------------------------------------------* > * #* > * # SITE- AND/OR PLATFORM-SPECIFIC DEFINITIONS. * > * #* > *#---------------------------------------------------------------------------* > ** > *#---------------------------------------------------------------------------* > * # Items in this file will need to be changed for each platform.* > *#---------------------------------------------------------------------------* > ** > *#---------------------------------------------------------------------------* > * # Parallel Fortran:* > * #* > * # For CG, EP, FT, MG, LU, SP and BT, which are in Fortran, the > following must * > * # be defined:* > * #* > * # MPIF77 - Fortran compiler* > * # FFLAGS - Fortran compilation arguments* > * # FMPI_INC - any -I arguments required for compiling MPI/Fortran * > * # FLINK - Fortran linker* > * # FLINKFLAGS - Fortran linker arguments* > * # FMPI_LIB - any -L and -l arguments required for linking > MPI/Fortran * > * # * > * # compilations are done with $(MPIF77) $(FMPI_INC) $(FFLAGS) or* > * # $(MPIF77) $(FFLAGS)* > * # linking is done with $(FLINK) $(FMPI_LIB) $(FLINKFLAGS)* > *#---------------------------------------------------------------------------* > ** > *#---------------------------------------------------------------------------* > * # This is the fortran compiler used for MPI programs* > *#---------------------------------------------------------------------------* > * MPIF77 = gfortran* > * # This links MPI fortran programs; usually the same as ${MPIF77}* > * FLINK= $(MPIF77)* > ** > *#---------------------------------------------------------------------------* > * # These macros are passed to the linker to help link with MPI > correctly* > *#---------------------------------------------------------------------------* > * FMPI_LIB = -L/share/apps/intel/impi/5.0.2.044/intel64/lib > <http://5.0.2.044/intel64/lib> -lmpi* > ** > ** > *#---------------------------------------------------------------------------* > * # These macros are passed to the compiler to help find 'mpif.h'* > *#---------------------------------------------------------------------------* > * FMPI_INC = -I/share/apps/intel/impi/5.0.2.044/intel64/include > <http://5.0.2.044/intel64/include>* > ** > *#---------------------------------------------------------------------------* > * # Global *compile time* flags for Fortran programs* > *#---------------------------------------------------------------------------* > * FFLAGS= -O* > ** > *#---------------------------------------------------------------------------* > * # Global *link time* flags. Flags for increasing maximum executable * > * # size usually go here. * > *#---------------------------------------------------------------------------* > * FLINKFLAGS = -O* > ** > ** > *#---------------------------------------------------------------------------* > * # Parallel C:* > * #* > * # For IS, which is in C, the following must be defined:* > * #* > * # MPICC - C compiler * > * # CFLAGS - C compilation arguments* > * # CMPI_INC - any -I arguments required for compiling MPI/C * > * # CLINK - C linker* > * # CLINKFLAGS - C linker flags* > * # CMPI_LIB - any -L and -l arguments required for linking MPI/C * > * #* > * # compilations are done with $(MPICC) $(CMPI_INC) $(CFLAGS) or* > * # $(MPICC) $(CFLAGS)* > * # linking is done with $(CLINK) $(CMPI_LIB) $(CLINKFLAGS)* > *#---------------------------------------------------------------------------* > ** > *#---------------------------------------------------------------------------* > * # This is the C compiler used for MPI programs* > *#---------------------------------------------------------------------------* > * MPICC = cc* > * # This links MPI C programs; usually the same as ${MPICC}* > * CLINK= $(MPICC)* > ** > *#---------------------------------------------------------------------------* > * # These macros are passed to the linker to help link with MPI > correctly* > *#---------------------------------------------------------------------------* > * CMPI_LIB = -L/usr/local/lib -lmpi* > ** > *#---------------------------------------------------------------------------* > * # These macros are passed to the compiler to help find 'mpi.h'* > *#---------------------------------------------------------------------------* > * CMPI_INC = -I/usr/local/include* > ** > *#---------------------------------------------------------------------------* > * # Global *compile time* flags for C programs* > *#---------------------------------------------------------------------------* > * CFLAGS= -O* > ** > *#---------------------------------------------------------------------------* > * # Global *link time* flags. Flags for increasing maximum executable * > * # size usually go here. * > *#---------------------------------------------------------------------------* > * CLINKFLAGS = -O* > ** > ** > *#---------------------------------------------------------------------------* > * # MPI dummy library:* > * #* > * # Uncomment if you want to use the MPI dummy library supplied by > NAS instead * > * # of the true message-passing library. The include file redefines > several of* > * # the above macros. It also invokes make in subdirectory > MPI_dummy. Make * > * # sure that no spaces or tabs precede include.* > *#---------------------------------------------------------------------------* > * # include ../config/make.dummy* > ** > ** > *#---------------------------------------------------------------------------* > * # Utilities C:* > * #* > * # This is the C compiler used to compile C utilities. Flags > required by * > * # this compiler go here also; typically there are few flags > required; hence * > * # there are no separate macros provided for such flags.* > *#---------------------------------------------------------------------------* > * CC= cc -g* > ** > ** > *#---------------------------------------------------------------------------* > * # Destination of executables, relative to subdirs of the main > directory. . * > *#---------------------------------------------------------------------------* > * BINDIR= ../bin* > ** > ** > *#---------------------------------------------------------------------------* > * # Some machines (e.g. Crays) have 128-bit DOUBLE PRECISION > numbers, which* > * # is twice the precision required for the NPB suite. A compiler > flag * > * # (e.g. -dp) can usually be used to change DOUBLE PRECISION > variables to* > * # 64 bits, but the MPI library may continue to send 128 bits. > Short of* > * # recompiling MPI, the solution is to use MPI_REAL to send these > 64-bit* > * # numbers, and MPI_COMPLEX to send their complex counterparts. > Uncomment* > * # the following line to enable this substitution. * > * # * > * # NOTE: IF THE I/O BENCHMARK IS BEING BUILT, WE USE CONVERTFLAG TO* > * # SPECIFIY THE FORTRAN RECORD LENGTH UNIT. IT IS A > SYSTEM-SPECIFIC* > * # VALUE (USUALLY 1 OR 4). UNCOMMENT THE SECOND LINE AND > SUBSTITUTE* > * # THE CORRECT VALUE FOR "length".* > * # IF BOTH 128-BIT DOUBLE PRECISION NUMBERS AND I/O ARE TO > BE ENABLED,* > * # UNCOMMENT THE THIRD LINE AND SUBSTITUTE THE CORRECT VALUE > FOR* > * # "length"* > *#---------------------------------------------------------------------------* > * # CONVERTFLAG= -DCONVERTDOUBLE* > * # CONVERTFLAG= -DFORTRAN_REC_SIZE=length* > * # CONVERTFLAG= -DCONVERTDOUBLE -DFORTRAN_REC_SIZE=length* > ** > ** > *#---------------------------------------------------------------------------* > * # The variable RAND controls which random number generator * > * # is used. It is described in detail in README.install. * > * # Use "randi8" unless there is a reason to use another one. * > * # Other allowed values are "randi8_safe", "randdp" and "randdpvec"* > *#---------------------------------------------------------------------------* > * RAND = randi8* > * # The following is highly reliable but may be slow:* > * # RAND = randdp* > > > > > > When I try to build let's say EP benchmark ***make NPROCS=8 EP > CLASS=C***, I get an error like > > * =========================================* > * = NAS Parallel Benchmarks 3.3 =* > * = MPI/F77/C =* > * =========================================* > ** > * cd EP; make NPROCS=8 CLASS=C* > * make[1]: Entering directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/EP'* > * make[2]: Entering directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/sys'* > * cc -g -o setparams setparams.c* > * make[2]: Leaving directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/sys'* > * ../sys/setparams ep 8 C* > * make.def modified. Rebuilding npbparams.h just in case* > * rm -f npbparams.h* > * ../sys/setparams ep 8 C* > * gfortran -c -I/share/apps/intel/impi/5.0.2.044/intel64/include > <http://5.0.2.044/intel64/include> -O ep.f* > * gfortran -O -o ../bin/ep.C.8 ep.o ../common/print_results.o > ../common/randi8.o ../common/timers.o -L/share/app > s/intel/impi/5.0.2.044/intel64/lib <http://5.0.2.044/intel64/lib> -lmpi* > * ep.o: In function `MAIN__':* > * ep.f:(.text+0x31): undefined reference to `mpi_init_'* > * ep.f:(.text+0x4b): undefined reference to `mpi_comm_rank_'* > * ep.f:(.text+0x65): undefined reference to `mpi_comm_size_'* > * ep.f:(.text+0x347): undefined reference to `mpi_abort_'* > * ep.f:(.text+0x3df): undefined reference to `mpi_barrier_'* > * ep.f:(.text+0x803): undefined reference to `mpi_allreduce_'* > * ep.f:(.text+0x842): undefined reference to `mpi_allreduce_'* > * ep.f:(.text+0x879): undefined reference to `mpi_allreduce_'* > * ep.f:(.text+0x935): undefined reference to `mpi_allreduce_'* > * ep.f:(.text+0xc70): undefined reference to `mpi_finalize_'* > * ../common/timers.o: In function `timer_stop_':* > * timers.f:(.text+0x27): undefined reference to `mpi_wtime_'* > * ../common/timers.o: In function `timer_start_':* > * timers.f:(.text+0x57): undefined reference to `mpi_wtime_'* > * collect2: ld returned 1 exit status* > * make[1]: *** [../bin/ep.C.8] Error 1* > * make[1]: Leaving directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/EP'* > * make: *** [ep] Error 2* > > > Can anybody please help me in resolving this issue? > > Thanks > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Antonio J. Peña Postdoctoral Appointee Mathematics and Computer Science Division Argonne National Laboratory 9700 South Cass Avenue, Bldg. 240, Of. 3148 Argonne, IL 60439-4847 apenya(a)mcs.anl.gov www.mcs.anl.gov/~apenya _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Error while building NAS benchmarks
by koko jumbo 02 Jun '15

02 Jun '15

I am trying to build NAS benchmarks using Intel MPI and below is the makefile that I am using. * #---------------------------------------------------------------------------* * #* * # SITE- AND/OR PLATFORM-SPECIFIC DEFINITIONS. * * #* * #---------------------------------------------------------------------------* * #---------------------------------------------------------------------------* * # Items in this file will need to be changed for each platform.* * #---------------------------------------------------------------------------* * #---------------------------------------------------------------------------* * # Parallel Fortran:* * #* * # For CG, EP, FT, MG, LU, SP and BT, which are in Fortran, the following must * * # be defined:* * #* * # MPIF77 - Fortran compiler* * # FFLAGS - Fortran compilation arguments* * # FMPI_INC - any -I arguments required for compiling MPI/Fortran * * # FLINK - Fortran linker* * # FLINKFLAGS - Fortran linker arguments* * # FMPI_LIB - any -L and -l arguments required for linking MPI/Fortran * * # * * # compilations are done with $(MPIF77) $(FMPI_INC) $(FFLAGS) or* * # $(MPIF77) $(FFLAGS)* * # linking is done with $(FLINK) $(FMPI_LIB) $(FLINKFLAGS)* * #---------------------------------------------------------------------------* * #---------------------------------------------------------------------------* * # This is the fortran compiler used for MPI programs* * #---------------------------------------------------------------------------* * MPIF77 = gfortran* * # This links MPI fortran programs; usually the same as ${MPIF77}* * FLINK = $(MPIF77)* * #---------------------------------------------------------------------------* * # These macros are passed to the linker to help link with MPI correctly* * #---------------------------------------------------------------------------* * FMPI_LIB = -L/share/apps/intel/impi/5.0.2.044/intel64/lib <http://5.0.2.044/intel64/lib> -lmpi* * #---------------------------------------------------------------------------* * # These macros are passed to the compiler to help find 'mpif.h'* * #---------------------------------------------------------------------------* * FMPI_INC = -I/share/apps/intel/impi/5.0.2.044/intel64/include <http://5.0.2.044/intel64/include>* * #---------------------------------------------------------------------------* * # Global *compile time* flags for Fortran programs* * #---------------------------------------------------------------------------* * FFLAGS = -O* * #---------------------------------------------------------------------------* * # Global *link time* flags. Flags for increasing maximum executable * * # size usually go here. * * #---------------------------------------------------------------------------* * FLINKFLAGS = -O* * #---------------------------------------------------------------------------* * # Parallel C:* * #* * # For IS, which is in C, the following must be defined:* * #* * # MPICC - C compiler * * # CFLAGS - C compilation arguments* * # CMPI_INC - any -I arguments required for compiling MPI/C * * # CLINK - C linker* * # CLINKFLAGS - C linker flags* * # CMPI_LIB - any -L and -l arguments required for linking MPI/C * * #* * # compilations are done with $(MPICC) $(CMPI_INC) $(CFLAGS) or* * # $(MPICC) $(CFLAGS)* * # linking is done with $(CLINK) $(CMPI_LIB) $(CLINKFLAGS)* * #---------------------------------------------------------------------------* * #---------------------------------------------------------------------------* * # This is the C compiler used for MPI programs* * #---------------------------------------------------------------------------* * MPICC = cc* * # This links MPI C programs; usually the same as ${MPICC}* * CLINK = $(MPICC)* * #---------------------------------------------------------------------------* * # These macros are passed to the linker to help link with MPI correctly* * #---------------------------------------------------------------------------* * CMPI_LIB = -L/usr/local/lib -lmpi* * #---------------------------------------------------------------------------* * # These macros are passed to the compiler to help find 'mpi.h'* * #---------------------------------------------------------------------------* * CMPI_INC = -I/usr/local/include* * #---------------------------------------------------------------------------* * # Global *compile time* flags for C programs* * #---------------------------------------------------------------------------* * CFLAGS = -O* * #---------------------------------------------------------------------------* * # Global *link time* flags. Flags for increasing maximum executable * * # size usually go here. * * #---------------------------------------------------------------------------* * CLINKFLAGS = -O* * #---------------------------------------------------------------------------* * # MPI dummy library:* * #* * # Uncomment if you want to use the MPI dummy library supplied by NAS instead * * # of the true message-passing library. The include file redefines several of* * # the above macros. It also invokes make in subdirectory MPI_dummy. Make * * # sure that no spaces or tabs precede include.* * #---------------------------------------------------------------------------* * # include ../config/make.dummy* * #---------------------------------------------------------------------------* * # Utilities C:* * #* * # This is the C compiler used to compile C utilities. Flags required by * * # this compiler go here also; typically there are few flags required; hence * * # there are no separate macros provided for such flags.* * #---------------------------------------------------------------------------* * CC = cc -g* * #---------------------------------------------------------------------------* * # Destination of executables, relative to subdirs of the main directory. . * * #---------------------------------------------------------------------------* * BINDIR = ../bin* * #---------------------------------------------------------------------------* * # Some machines (e.g. Crays) have 128-bit DOUBLE PRECISION numbers, which* * # is twice the precision required for the NPB suite. A compiler flag * * # (e.g. -dp) can usually be used to change DOUBLE PRECISION variables to* * # 64 bits, but the MPI library may continue to send 128 bits. Short of* * # recompiling MPI, the solution is to use MPI_REAL to send these 64-bit* * # numbers, and MPI_COMPLEX to send their complex counterparts. Uncomment* * # the following line to enable this substitution. * * # * * # NOTE: IF THE I/O BENCHMARK IS BEING BUILT, WE USE CONVERTFLAG TO* * # SPECIFIY THE FORTRAN RECORD LENGTH UNIT. IT IS A SYSTEM-SPECIFIC* * # VALUE (USUALLY 1 OR 4). UNCOMMENT THE SECOND LINE AND SUBSTITUTE* * # THE CORRECT VALUE FOR "length".* * # IF BOTH 128-BIT DOUBLE PRECISION NUMBERS AND I/O ARE TO BE ENABLED,* * # UNCOMMENT THE THIRD LINE AND SUBSTITUTE THE CORRECT VALUE FOR* * # "length"* * #---------------------------------------------------------------------------* * # CONVERTFLAG = -DCONVERTDOUBLE* * # CONVERTFLAG = -DFORTRAN_REC_SIZE=length* * # CONVERTFLAG = -DCONVERTDOUBLE -DFORTRAN_REC_SIZE=length* * #---------------------------------------------------------------------------* * # The variable RAND controls which random number generator * * # is used. It is described in detail in README.install. * * # Use "randi8" unless there is a reason to use another one. * * # Other allowed values are "randi8_safe", "randdp" and "randdpvec"* * #---------------------------------------------------------------------------* * RAND = randi8* * # The following is highly reliable but may be slow:* * # RAND = randdp* When I try to build let's say EP benchmark ***make NPROCS=8 EP CLASS=C***, I get an error like * =========================================* * = NAS Parallel Benchmarks 3.3 =* * = MPI/F77/C =* * =========================================* * cd EP; make NPROCS=8 CLASS=C* * make[1]: Entering directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/EP'* * make[2]: Entering directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/sys'* * cc -g -o setparams setparams.c* * make[2]: Leaving directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/sys'* * ../sys/setparams ep 8 C* * make.def modified. Rebuilding npbparams.h just in case* * rm -f npbparams.h* * ../sys/setparams ep 8 C* * gfortran -c -I/share/apps/intel/impi/5.0.2.044/intel64/include <http://5.0.2.044/intel64/include> -O ep.f* * gfortran -O -o ../bin/ep.C.8 ep.o ../common/print_results.o ../common/randi8.o ../common/timers.o -L/share/app s/intel/impi/5.0.2.044/intel64/lib <http://5.0.2.044/intel64/lib> -lmpi* * ep.o: In function `MAIN__':* * ep.f:(.text+0x31): undefined reference to `mpi_init_'* * ep.f:(.text+0x4b): undefined reference to `mpi_comm_rank_'* * ep.f:(.text+0x65): undefined reference to `mpi_comm_size_'* * ep.f:(.text+0x347): undefined reference to `mpi_abort_'* * ep.f:(.text+0x3df): undefined reference to `mpi_barrier_'* * ep.f:(.text+0x803): undefined reference to `mpi_allreduce_'* * ep.f:(.text+0x842): undefined reference to `mpi_allreduce_'* * ep.f:(.text+0x879): undefined reference to `mpi_allreduce_'* * ep.f:(.text+0x935): undefined reference to `mpi_allreduce_'* * ep.f:(.text+0xc70): undefined reference to `mpi_finalize_'* * ../common/timers.o: In function `timer_stop_':* * timers.f:(.text+0x27): undefined reference to `mpi_wtime_'* * ../common/timers.o: In function `timer_start_':* * timers.f:(.text+0x57): undefined reference to `mpi_wtime_'* * collect2: ld returned 1 exit status* * make[1]: *** [../bin/ep.C.8] Error 1* * make[1]: Leaving directory `/home/vaibhavs/NPB3.3/NPB3.3-MPI/EP'* * make: *** [ep] Error 2* Can anybody please help me in resolving this issue? Thanks _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH and sudo mpiexec
by Thibault, Daniel 02 Jun '15

02 Jun '15

I have a small network of machines all running the same OS (Linaro Ubuntu Linux); they were all cloned from the same disk image and differ only in their machine names (UNIT1 through UNIT4). I can ssh between them at will, trusty has been established and I no longer get asked for a password upon connecting. MPICH is installed from the Ubuntu repository (not quite the latest version: mpiexec reports version OpenRTE 1.8.1, the mpich package is 3.0.4-6ubuntu1), and I can run a demo like cpi with no issues, using a little mpi-run.sh bash script (the default shell is tcsh, however) : (begin script) #!/bin/bash set -e ESDK=${EPIPHANY_HOME} ELIBS=${ESDK}/tools/host/lib:${LD_LIBRARY_PATH} EHDF=${EPIPHANY_HDF} echo "Running cpi on machines.u2.mpi" LD_LIBRARY_PATH=${ELIBS} mpiexec --allow-run-as-root -machinefile /home/linaro/.machines.u2.mpi -n 1 /home/linaro/myMPI/cpi echo "Done!" (end script) .machines.u2.mpi consists of the one line: linaro@UNIT2

1 0

execution time
by Chafik sanaa 02 Jun '15

02 Jun '15

hi, i want execute my MPI program but i haven't a parallel machine, it is that there is no a way to do it online in a site, or a free application ... because in my machine does not give the real execution time. _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH issue when running jobs in background
by Roy, Hirak 02 Jun '15

02 Jun '15

Hi Team, I am using MPICH 3.0.4. My top level script invokes a 'batch script' in background and then runs my mpi-program using mpiexec. I run this top-level script in background mode ( please check details later). It seems once I invoke the mpiexec, my batch-script execution is suspended. I tried OpenMPI and they do not have the issue. I have attached 3 files. 1> run.sh : run script to run the top-level program 2> background.sh : invoked from run.sh as a background job. Just prints something on a while loop 3> myprog.c : simple MPI program which just waits on a loop Compile step : mpicc myprog.c --> a.out #! /bin/bash ./background.sh & mpiexec -n 1 ./a.out To reproduce : Shell >> ./run.sh & Shell >> jobs [1] + Suspended (tty input) ./run.sh Here the background.sh is suspended. However, a.out keeps running. If I change the script so that mpiexec takes input from /dev/null, then the issue is resolved. #! /bin/bash ./background.sh & mpiexec -n 1 ./a.out < /dev/null It seems to be a MPICH specific issue. Could you please have a look and file a bug for this. Thanks, Hirak _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] OFI
by Kenneth Raffenetti 01 Jun '15

01 Jun '15

Hi Eva, To build support for OFI in MPICH, add --with-device=ch3:nemesis:ofi to your configure line. The OFI netmod passes almost all tests in the MPICH testsuite and should be usable with most benchmark suites. Ken On 06/01/2015 01:19 AM, Eva Mishra wrote: > Hello > what benchmarks can be run over OFI using the current mpich source ? > how do we select OFI path in mpich ? > Regards > Eva Mishra > > ------------------------------------------------------------------------------------------------------------------------------- > > [ C-DAC is on Social-Media too. Kindly follow us at: > Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] > > This e-mail is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. If you are not the > intended recipient, please contact the sender by reply e-mail and destroy > all copies and the original message. Any unauthorized review, use, > disclosure, dissemination, forwarding, printing or copying of this email > is strictly prohibited and appropriate legal action will be taken. > ------------------------------------------------------------------------------------------------------------------------------- > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

OFI
by Eva Mishra 01 Jun '15

01 Jun '15

Hello what benchmarks can be run over OFI using the current mpich source ? how do we select OFI path in mpich ? Regards Eva Mishra ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken. ------------------------------------------------------------------------------------------------------------------------------- _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0