November 2013 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Assembler messages at build ?
by "Antonio J. Peña" 23 Nov '13

23 Nov '13

Lou, Your c.txt file seems to be a configure log. We need the log of your compilation step. There's nothing obviously wrong in your configure logs. Antonio On 11/23/2013 06:14 PM, Lou Picciano wrote: > Antonio, Tks for taking a look at this. config.log and c.txt are attached. > > (Pardon the noob typo error - Duh! Yes, config is with 'CFLAGS' - no, not cross-compiling) > > Lou > > ----- Original Message ----- > From: "Antonio J. Pena" <apenya(a)mcs.anl.gov> > To: discuss(a)mpich.org > Sent: Saturday, November 23, 2013 1:11:38 PM > Subject: Re: [mpich-discuss] Assembler messages at build ? > > > Hi Lou, > > First, CFLAGFS should be CFLAGS. Anyway, that should be the default in a 32- > bit system, so irrelevant unless you're cross-compiling. If that's not the > case, please attach config.log and c.txt so that we can take a look. All of > our 32-bit test builds compile without problems. > > Thanks, > Antonio > > > On Saturday, November 23, 2013 05:13:28 PM Lou Picciano wrote: >> mpich Wizards, >> >> Trying our first build of mpich-3.0.4, and seeing Assembler messages at >> build time: (there are clearly a lot of config options to become familiar >> with; but, as a first pass): >> >> Configure is: >> ./configure --prefix=/usr/local/mpi32 \ >> CFLAGFS="-m32" FFLAGS="-m32" \ >> >> | tee c.txt >> >> $ make >> ... >> CC src/mpi/attr/attrutil.lo >> CC src/mpi/attr/dup_fn.lo >> CC src/mpi/coll/allred_group.lo >> CC src/mpi/coll/barrier_group.lo >> CC src/mpi/coll/helper_fns.lo >> /var/tmp//ccf4aaqC.s: Assembler messages: >> /var/tmp//ccf4aaqC.s:851: Error: number of operands mismatch for `mov' >> /var/tmp//ccf4aaqC.s:859: Error: number of operands mismatch for `mov' >> make[2]: *** [src/mpi/coll/helper_fns.lo] Error 1 >> make[2]: Leaving directory `<build_path>/mpich-3.0.4' >> make[1]: *** [all-recursive] Error 1 >> >> gcc 4.7.3 >> Platform is i86 OpenIndiana (Illumos, Solaris-ish) >> >> Can anyone point me in the right direction? >> >> Lou >> _______________________________________________ >> 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 > > > _______________________________________________ > 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] Assembler messages at build ?
by Lou Picciano 23 Nov '13

23 Nov '13

Antonio, Tks for taking a look at this. config.log and c.txt are attached. (Pardon the noob typo error - Duh! Yes, config is with 'CFLAGS' - no, not cross-compiling) Lou ----- Original Message ----- From: "Antonio J. Pena" <apenya(a)mcs.anl.gov> To: discuss(a)mpich.org Sent: Saturday, November 23, 2013 1:11:38 PM Subject: Re: [mpich-discuss] Assembler messages at build ? Hi Lou, First, CFLAGFS should be CFLAGS. Anyway, that should be the default in a 32- bit system, so irrelevant unless you're cross-compiling. If that's not the case, please attach config.log and c.txt so that we can take a look. All of our 32-bit test builds compile without problems. Thanks, Antonio On Saturday, November 23, 2013 05:13:28 PM Lou Picciano wrote: > mpich Wizards, > > Trying our first build of mpich-3.0.4, and seeing Assembler messages at > build time: (there are clearly a lot of config options to become familiar > with; but, as a first pass): > > Configure is: > ./configure --prefix=/usr/local/mpi32 \ > CFLAGFS="-m32" FFLAGS="-m32" \ > > | tee c.txt > > $ make > ... > CC src/mpi/attr/attrutil.lo > CC src/mpi/attr/dup_fn.lo > CC src/mpi/coll/allred_group.lo > CC src/mpi/coll/barrier_group.lo > CC src/mpi/coll/helper_fns.lo > /var/tmp//ccf4aaqC.s: Assembler messages: > /var/tmp//ccf4aaqC.s:851: Error: number of operands mismatch for `mov' > /var/tmp//ccf4aaqC.s:859: Error: number of operands mismatch for `mov' > make[2]: *** [src/mpi/coll/helper_fns.lo] Error 1 > make[2]: Leaving directory `<build_path>/mpich-3.0.4' > make[1]: *** [all-recursive] Error 1 > > gcc 4.7.3 > Platform is i86 OpenIndiana (Illumos, Solaris-ish) > > Can anyone point me in the right direction? > > Lou > _______________________________________________ > 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

Re: [mpich-discuss] Assembler messages at build ?
by Antonio J. Pena 23 Nov '13

23 Nov '13

Hi Lou, First, CFLAGFS should be CFLAGS. Anyway, that should be the default in a 32- bit system, so irrelevant unless you're cross-compiling. If that's not the case, please attach config.log and c.txt so that we can take a look. All of our 32-bit test builds compile without problems. Thanks, Antonio On Saturday, November 23, 2013 05:13:28 PM Lou Picciano wrote: > mpich Wizards, > > Trying our first build of mpich-3.0.4, and seeing Assembler messages at > build time: (there are clearly a lot of config options to become familiar > with; but, as a first pass): > > Configure is: > ./configure --prefix=/usr/local/mpi32 \ > CFLAGFS="-m32" FFLAGS="-m32" \ > > | tee c.txt > > $ make > ... > CC src/mpi/attr/attrutil.lo > CC src/mpi/attr/dup_fn.lo > CC src/mpi/coll/allred_group.lo > CC src/mpi/coll/barrier_group.lo > CC src/mpi/coll/helper_fns.lo > /var/tmp//ccf4aaqC.s: Assembler messages: > /var/tmp//ccf4aaqC.s:851: Error: number of operands mismatch for `mov' > /var/tmp//ccf4aaqC.s:859: Error: number of operands mismatch for `mov' > make[2]: *** [src/mpi/coll/helper_fns.lo] Error 1 > make[2]: Leaving directory `<build_path>/mpich-3.0.4' > make[1]: *** [all-recursive] Error 1 > > gcc 4.7.3 > Platform is i86 OpenIndiana (Illumos, Solaris-ish) > > Can anyone point me in the right direction? > > Lou > _______________________________________________ > 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] first attempts with neighbor collectives
by Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation] 23 Nov '13

23 Nov '13

Declaring sdispls and rdispls as integer(kind=MPI_ADDRESS_KIND) does resolve the failure and the output from MPI_Neighbor_alltoallw agrees with the other neighbor routines. Thank you Daniel Kokron NASA Ames (ARC-TN) SciCon group 301-286-3959 ________________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Rajeev Thakur [thakur(a)mcs.anl.gov] Sent: Saturday, November 23, 2013 12:07 AM To: discuss(a)mpich.org Subject: Re: [mpich-discuss] first attempts with neighbor collectives In alltoallw, sdispls and rdispls need to be defined as integer (kind=MPI_ADDRESS_KIND). MPI_Comm_free(cart) needs an ierr. In Fortran you should use MPI_INTEGER instead of MPI_INT as the datatype. Rajeev On Nov 22, 2013, at 2:20 PM, "Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation]" <daniel.s.kokron(a)nasa.gov> wrote: > I've started playing with the neighbor collectives in mpich-3.0.4. My first attempt was to convert the existing ~/test/mpi/topo/neighb_coll.c from 1D to 2D. That went fine. Now I want to convert that 2D C code to fortran. All works fine except the call to MPI_Neighbor_alltoallw which fails with a SEGV. Any ideas what I'm going wrong? > > My 3.0.4 was configured and compiled with the Intel 13.1.3.192 compiler suite under Linux kernel 2.6.32.54 x86_64. > ./configure CC=icc CXX=icpc FC=ifort F77=ifort --prefix=~/install/intel-13.1.3.192 --enable-f77 --enable-fc --enable-g=all --enable-debuginfo --enable-shared > > The attached reproducer was compiled with the same suite > mpif90 -g -O0 -traceback -debug -check -o neighb_coll2Df neighb_coll2Df.f90 > > and run with > mpirun -np 12 neighb_coll2Df > > > valgrind-3.8.1 had this to say > ==55631== Conditional jump or move depends on uninitialised value(s) > ==55631== at 0x62A9F42: vfprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x62CD288: vsprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x62B2BD7: sprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x47288B: stackwalk_cb (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x473B94: tbk_trace_stack (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x4725E5: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) > ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) > ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) > ==55631== > ==55631== Warning: bad signal number 0 in sigaction() > ==55631== Conditional jump or move depends on uninitialised value(s) > ==55631== at 0x47263A: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) > ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) > ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) > ==55631== by 0x5139960: MPID_nem_mpich_sendv_header (mpid_nem_inline.h:307) > ==55631== by 0x5137847: MPIDI_CH3_iSendv (ch3_isendv.c:74) > ==55631== by 0x5119825: MPIDI_CH3_EagerContigIsend (ch3u_eager.c:550) > ==55631== by 0x5123A47: MPID_Isend (mpid_isend.c:131) > ==55631== by 0x518A974: MPID_Sched_start (mpid_sched.c:155) > > Daniel Kokron > NASA Ames (ARC-TN) > SciCon group > 301-286-3959 > <neighb_coll2Df.f90>_______________________________________________ > 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

Assembler messages at build ?
by Lou Picciano 23 Nov '13

23 Nov '13

mpich Wizards, Trying our first build of mpich-3.0.4, and seeing Assembler messages at build time: (there are clearly a lot of config options to become familiar with; but, as a first pass): Configure is: ./configure --prefix=/usr/local/mpi32 \ CFLAGFS="-m32" FFLAGS="-m32" \ | tee c.txt $ make ... CC src/mpi/attr/attrutil.lo CC src/mpi/attr/dup_fn.lo CC src/mpi/coll/allred_group.lo CC src/mpi/coll/barrier_group.lo CC src/mpi/coll/helper_fns.lo /var/tmp//ccf4aaqC.s: Assembler messages: /var/tmp//ccf4aaqC.s:851: Error: number of operands mismatch for `mov' /var/tmp//ccf4aaqC.s:859: Error: number of operands mismatch for `mov' make[2]: *** [src/mpi/coll/helper_fns.lo] Error 1 make[2]: Leaving directory `<build_path>/mpich-3.0.4' make[1]: *** [all-recursive] Error 1 gcc 4.7.3 Platform is i86 OpenIndiana (Illumos, Solaris-ish) Can anyone point me in the right direction? Lou

1 0

Re: [mpich-discuss] first attempts with neighbor collectives
by Rajeev Thakur 22 Nov '13

22 Nov '13

In alltoallw, sdispls and rdispls need to be defined as integer (kind=MPI_ADDRESS_KIND). MPI_Comm_free(cart) needs an ierr. In Fortran you should use MPI_INTEGER instead of MPI_INT as the datatype. Rajeev On Nov 22, 2013, at 2:20 PM, "Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation]" <daniel.s.kokron(a)nasa.gov> wrote: > I've started playing with the neighbor collectives in mpich-3.0.4. My first attempt was to convert the existing ~/test/mpi/topo/neighb_coll.c from 1D to 2D. That went fine. Now I want to convert that 2D C code to fortran. All works fine except the call to MPI_Neighbor_alltoallw which fails with a SEGV. Any ideas what I'm going wrong? > > My 3.0.4 was configured and compiled with the Intel 13.1.3.192 compiler suite under Linux kernel 2.6.32.54 x86_64. > ./configure CC=icc CXX=icpc FC=ifort F77=ifort --prefix=~/install/intel-13.1.3.192 --enable-f77 --enable-fc --enable-g=all --enable-debuginfo --enable-shared > > The attached reproducer was compiled with the same suite > mpif90 -g -O0 -traceback -debug -check -o neighb_coll2Df neighb_coll2Df.f90 > > and run with > mpirun -np 12 neighb_coll2Df > > > valgrind-3.8.1 had this to say > ==55631== Conditional jump or move depends on uninitialised value(s) > ==55631== at 0x62A9F42: vfprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x62CD288: vsprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x62B2BD7: sprintf (in /lib64/libc-2.11.1.so) > ==55631== by 0x47288B: stackwalk_cb (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x473B94: tbk_trace_stack (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x4725E5: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) > ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) > ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) > ==55631== > ==55631== Warning: bad signal number 0 in sigaction() > ==55631== Conditional jump or move depends on uninitialised value(s) > ==55631== at 0x47263A: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) > ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) > ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) > ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) > ==55631== by 0x5139960: MPID_nem_mpich_sendv_header (mpid_nem_inline.h:307) > ==55631== by 0x5137847: MPIDI_CH3_iSendv (ch3_isendv.c:74) > ==55631== by 0x5119825: MPIDI_CH3_EagerContigIsend (ch3u_eager.c:550) > ==55631== by 0x5123A47: MPID_Isend (mpid_isend.c:131) > ==55631== by 0x518A974: MPID_Sched_start (mpid_sched.c:155) > > Daniel Kokron > NASA Ames (ARC-TN) > SciCon group > 301-286-3959 > <neighb_coll2Df.f90>_______________________________________________ > 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] first attempts with neighbor collectives
by Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation] 22 Nov '13

22 Nov '13

mpich-3.1rc2 has gives the same result. Daniel Kokron NASA Ames (ARC-TN) SciCon group 301-286-3959 ________________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation] [daniel.s.kokron(a)nasa.gov] Sent: Friday, November 22, 2013 3:20 PM To: discuss(a)mpich.org Subject: [mpich-discuss] first attempts with neighbor collectives I've started playing with the neighbor collectives in mpich-3.0.4. My first attempt was to convert the existing ~/test/mpi/topo/neighb_coll.c from 1D to 2D. That went fine. Now I want to convert that 2D C code to fortran. All works fine except the call to MPI_Neighbor_alltoallw which fails with a SEGV. Any ideas what I'm going wrong? My 3.0.4 was configured and compiled with the Intel 13.1.3.192 compiler suite under Linux kernel 2.6.32.54 x86_64. ./configure CC=icc CXX=icpc FC=ifort F77=ifort --prefix=~/install/intel-13.1.3.192 --enable-f77 --enable-fc --enable-g=all --enable-debuginfo --enable-shared The attached reproducer was compiled with the same suite mpif90 -g -O0 -traceback -debug -check -o neighb_coll2Df neighb_coll2Df.f90 and run with mpirun -np 12 neighb_coll2Df valgrind-3.8.1 had this to say ==55631== Conditional jump or move depends on uninitialised value(s) ==55631== at 0x62A9F42: vfprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x62CD288: vsprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x62B2BD7: sprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x47288B: stackwalk_cb (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x473B94: tbk_trace_stack (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x4725E5: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) ==55631== ==55631== Warning: bad signal number 0 in sigaction() ==55631== Conditional jump or move depends on uninitialised value(s) ==55631== at 0x47263A: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) ==55631== by 0x5139960: MPID_nem_mpich_sendv_header (mpid_nem_inline.h:307) ==55631== by 0x5137847: MPIDI_CH3_iSendv (ch3_isendv.c:74) ==55631== by 0x5119825: MPIDI_CH3_EagerContigIsend (ch3u_eager.c:550) ==55631== by 0x5123A47: MPID_Isend (mpid_isend.c:131) ==55631== by 0x518A974: MPID_Sched_start (mpid_sched.c:155) Daniel Kokron NASA Ames (ARC-TN) SciCon group 301-286-3959

1 0

first attempts with neighbor collectives
by Kokron, Daniel S. (GSFC-610.1)[Computer Sciences Corporation] 22 Nov '13

22 Nov '13

I've started playing with the neighbor collectives in mpich-3.0.4. My first attempt was to convert the existing ~/test/mpi/topo/neighb_coll.c from 1D to 2D. That went fine. Now I want to convert that 2D C code to fortran. All works fine except the call to MPI_Neighbor_alltoallw which fails with a SEGV. Any ideas what I'm going wrong? My 3.0.4 was configured and compiled with the Intel 13.1.3.192 compiler suite under Linux kernel 2.6.32.54 x86_64. ./configure CC=icc CXX=icpc FC=ifort F77=ifort --prefix=~/install/intel-13.1.3.192 --enable-f77 --enable-fc --enable-g=all --enable-debuginfo --enable-shared The attached reproducer was compiled with the same suite mpif90 -g -O0 -traceback -debug -check -o neighb_coll2Df neighb_coll2Df.f90 and run with mpirun -np 12 neighb_coll2Df valgrind-3.8.1 had this to say ==55631== Conditional jump or move depends on uninitialised value(s) ==55631== at 0x62A9F42: vfprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x62CD288: vsprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x62B2BD7: sprintf (in /lib64/libc-2.11.1.so) ==55631== by 0x47288B: stackwalk_cb (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x473B94: tbk_trace_stack (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x4725E5: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) ==55631== ==55631== Warning: bad signal number 0 in sigaction() ==55631== Conditional jump or move depends on uninitialised value(s) ==55631== at 0x47263A: tbk_string_stack_signal (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x42ADE1: tbk_stack_trace (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40B89A: for__issue_diagnostic (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x40F034: for__signal_handler (in /home1/dkokron/play/MPICH3/mpich-3.0.4/test/mpi/topo/neighb_coll2Df) ==55631== by 0x5BFD5CF: ??? (in /lib64/libpthread-2.11.1.so) ==55631== by 0x4C2B01F: _intel_fast_memcpy (mc_replace_strmem.c:889) ==55631== by 0x5138DD5: MPIUI_Memcpy (mpiimpl.h:162) ==55631== by 0x5139960: MPID_nem_mpich_sendv_header (mpid_nem_inline.h:307) ==55631== by 0x5137847: MPIDI_CH3_iSendv (ch3_isendv.c:74) ==55631== by 0x5119825: MPIDI_CH3_EagerContigIsend (ch3u_eager.c:550) ==55631== by 0x5123A47: MPID_Isend (mpid_isend.c:131) ==55631== by 0x518A974: MPID_Sched_start (mpid_sched.c:155) Daniel Kokron NASA Ames (ARC-TN) SciCon group 301-286-3959

1 0

Re: [mpich-discuss] MPICH Page Hacked
by Ken Raffenetti 21 Nov '13

21 Nov '13

The MPICH site is back online. ----- Original Message ----- > From: "Ken Raffenetti" <raffenet(a)mcs.anl.gov> > To: marcelo(a)cebacad.net, discuss(a)mpich.org > Sent: Thursday, November 21, 2013 11:15:44 AM > Subject: Re: [mpich-discuss] MPICH Page Hacked > > We're blocking access to the site while this is fixed. > > ----- Original Message ----- > > From: "Marcelo Soares Souza" <marcelo(a)cebacad.net> > > To: discuss(a)mpich.org > > Sent: Thursday, November 21, 2013 10:51:13 AM > > Subject: [mpich-discuss] MPICH Page Hacked > > > > > > Hi, > > > > Apparently the main mpich.org was cracked. > > > > > > > > _______________________________________________ > > 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

Re: [mpich-discuss] MPICH Page Hacked
by Ken Raffenetti 21 Nov '13

21 Nov '13

We're blocking access to the site while this is fixed. ----- Original Message ----- > From: "Marcelo Soares Souza" <marcelo(a)cebacad.net> > To: discuss(a)mpich.org > Sent: Thursday, November 21, 2013 10:51:13 AM > Subject: [mpich-discuss] MPICH Page Hacked > > > Hi, > > Apparently the main mpich.org was cracked. > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss >

1 0