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

Error in compiling MPICH on Mac desktop
by Ghosh, Debojyoti 28 Oct '15

28 Oct '15

Hi, I am getting a compilation error while trying to compile MPICH on my Mac desktop. I installed the latest GNU compilers using Homebrew. > gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/5.2.0/libexec/gcc/x86_64-apple-darwin14.5.0/5.2.0/lto-wrapper Target: x86_64-apple-darwin14.5.0 Configured with: ../configure --build=x86_64-apple-darwin14.5.0 --prefix=/usr/local/Cellar/gcc/5.2.0 --libdir=/usr/local/Cellar/gcc/5.2.0/lib/gcc/5 --enable-languages=c,c++,objc,obj-c++,fortran --program-suffix=-5 --with-gmp=/usr/local/opt/gmp --with-mpfr=/usr/local/opt/mpfr --with-mpc=/usr/local/opt/libmpc --with-isl=/usr/local/opt/isl --with-system-zlib --enable-libstdcxx-time=yes --enable-stage1-checking --enable-checking=release --enable-lto --with-build-config=bootstrap-debug --disable-werror --with-pkgversion='Homebrew gcc 5.2.0' --with-bugurl=https://github.com/Homebrew/homebrew/issues --enable-plugin --disable-nls --enable-multilib Thread model: posix gcc version 5.2.0 (Homebrew gcc 5.2.0) I am getting the following error while compiling MPICH: CC src/mpltrmem.lo /var/folders/qf/q3tp7kgn0gz6qj5_c2nr4qqm001qq3/T//ccyirdXM.s:491:suffix or operands invalid for `movq' /var/folders/qf/q3tp7kgn0gz6qj5_c2nr4qqm001qq3/T//ccyirdXM.s:495:suffix or operands invalid for `movq' make[2]: *** [src/mpltrmem.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 I have attached the configure log c.txt and the make log m.txt. Thanks, Debo -- Debojyoti Ghosh ghosh5(a)llnl.gov<mailto:[email protected]> http://debog.github.io/ _______________________________________________ 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] problem after compilation
by Kenneth Raffenetti 26 Oct '15

26 Oct '15

In order to use MPICH, you need to ensure that PATH and LD_LIBRARY_PATH are consistent and point to the same installation location. If you used the OpenFOAM install instructions here: http://www.openfoam.org/download/source.php - you likely have conflicts with their MPI recommendation. Ken On 10/24/2015 10:48 AM, vinod pandey wrote: > the problem occured after I installed another software package > "openfoam". Earlier the code was running fine. > Please help. > Vinod > > On Fri, Oct 23, 2015 at 12:30 AM, vinod pandey <pandeyvinod4(a)gmail.com > <mailto:[email protected]>> wrote: > > I have followed the instructions while building and installing > mpich. I didnt face any problem in that part. Its just after > compilation that this error message occurs. > Vinod > > On Fri, Oct 23, 2015 at 12:19 AM, Balaji, Pavan <balaji(a)anl.gov > <mailto:[email protected]>> wrote: > > > It's best to go through the README for step-by-step instructions > on how to build mpich. > > -- Pavan > > From: vinod pandey <pandeyvinod4(a)gmail.com > <mailto:[email protected]>> > Reply-To: "discuss(a)mpich.org <mailto:[email protected]>" > <discuss(a)mpich.org <mailto:[email protected]>> > Date: Thursday, October 22, 2015 at 1:37 PM > To: "discuss(a)mpich.org <mailto:[email protected]>" > <discuss(a)mpich.org <mailto:[email protected]>> > Subject: Re: [mpich-discuss] problem after compilation > > Thanks for the reply but I am completely new to it. Can you > please suggest me what exactly I can do to avoid this error. > thanks and regards. > > On Thu, Oct 22, 2015 at 8:57 PM, Balaji, Pavan <balaji(a)anl.gov > <mailto:[email protected]>> wrote: > > > You seem to be mixing MPICH and a different MPI > implementation (probably Open MPI). > > From: vinod pandey <pandeyvinod4(a)gmail.com > <mailto:[email protected]>> > Reply-To: "discuss(a)mpich.org <mailto:[email protected]>" > <discuss(a)mpich.org <mailto:[email protected]>> > Date: Thursday, October 22, 2015 at 2:30 AM > To: "discuss(a)mpich.org <mailto:[email protected]>" > <discuss(a)mpich.org <mailto:[email protected]>> > Subject: [mpich-discuss] problem after compilation > > I am getting the below message after compilation > > /usr/bin/ld: warning: libmpi.so.1, needed by > /usr//lib/libmpi_f77.so, may conflict with libmpi.so.12 > > Kindly help. > -- > ............. > VINOD PANDEY > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > ............. > VINOD PANDEY > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > ............. > VINOD PANDEY > > > > > -- > ............. > VINOD PANDEY > > > _______________________________________________ > 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] problem after compilation
by vinod pandey 24 Oct '15

24 Oct '15

the problem occured after I installed another software package "openfoam". Earlier the code was running fine. Please help. Vinod On Fri, Oct 23, 2015 at 12:30 AM, vinod pandey <pandeyvinod4(a)gmail.com> wrote: > I have followed the instructions while building and installing mpich. I > didnt face any problem in that part. Its just after compilation that this > error message occurs. > Vinod > > On Fri, Oct 23, 2015 at 12:19 AM, Balaji, Pavan <balaji(a)anl.gov> wrote: > >> >> It's best to go through the README for step-by-step instructions on how >> to build mpich. >> >> -- Pavan >> >> From: vinod pandey <pandeyvinod4(a)gmail.com> >> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> >> Date: Thursday, October 22, 2015 at 1:37 PM >> To: "discuss(a)mpich.org" <discuss(a)mpich.org> >> Subject: Re: [mpich-discuss] problem after compilation >> >> Thanks for the reply but I am completely new to it. Can you please >> suggest me what exactly I can do to avoid this error. >> thanks and regards. >> >> On Thu, Oct 22, 2015 at 8:57 PM, Balaji, Pavan <balaji(a)anl.gov> wrote: >> >>> >>> You seem to be mixing MPICH and a different MPI implementation (probably >>> Open MPI). >>> >>> From: vinod pandey <pandeyvinod4(a)gmail.com> >>> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> >>> Date: Thursday, October 22, 2015 at 2:30 AM >>> To: "discuss(a)mpich.org" <discuss(a)mpich.org> >>> Subject: [mpich-discuss] problem after compilation >>> >>> I am getting the below message after compilation >>> >>> /usr/bin/ld: warning: libmpi.so.1, needed by /usr//lib/libmpi_f77.so, >>> may conflict with libmpi.so.12 >>> >>> Kindly help. >>> -- >>> ............. >>> VINOD PANDEY >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >> >> >> >> -- >> ............. >> VINOD PANDEY >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > > > -- > ............. > VINOD PANDEY > -- ............. VINOD PANDEY _______________________________________________ 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] Disabled fortran but mpichversion still mentions gfortran
by Jeff Hammond 23 Oct '15

23 Oct '15

I think you can configure explicitly with FC=false F77=false if you hate seeing gfortran mentioned there. Jeff On Fri, Oct 23, 2015 at 4:13 AM, Torquil Macdonald Sørensen < torquil(a)gmail.com> wrote: > Hi! > > I configured MPICH 3.2rc1 with --disable-cxx --disable-fortran, but the > executable "mpichversion" outputs > > $ mpichversion > > MPICH Version: 3.2rc1 > MPICH Release date: Mon Oct 5 16:16:43 CDT 2015 > MPICH Device: ch3:nemesis > MPICH configure: --prefix=/mn/anatu/cma-u3/tmac/usr/stow/mpich > --enable-shared --enable-static=no --disable-cxx --disable-fortran > MPICH CC: gcc -O2 > MPICH CXX: no > MPICH F77: gfortran > MPICH FC: gfortran > > Since it is written "MPICH CXX: no", perhaps it should also be written > "MPICH F77: no" and "MPICH FC: no"? I have verified that mpifort, mpif77 > and mpif90 are missing from bin/ (as they should). > > Best regards > Torquil Macdonald Sørensen > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Disabled fortran but mpichversion still mentions gfortran
by Torquil Macdonald Sørensen 23 Oct '15

23 Oct '15

Hi! I configured MPICH 3.2rc1 with --disable-cxx --disable-fortran, but the executable "mpichversion" outputs $ mpichversion MPICH Version: 3.2rc1 MPICH Release date: Mon Oct 5 16:16:43 CDT 2015 MPICH Device: ch3:nemesis MPICH configure: --prefix=/mn/anatu/cma-u3/tmac/usr/stow/mpich --enable-shared --enable-static=no --disable-cxx --disable-fortran MPICH CC: gcc -O2 MPICH CXX: no MPICH F77: gfortran MPICH FC: gfortran Since it is written "MPICH CXX: no", perhaps it should also be written "MPICH F77: no" and "MPICH FC: no"? I have verified that mpifort, mpif77 and mpif90 are missing from bin/ (as they should). Best regards Torquil Macdonald Sørensen _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Meet us at SC '15
by Seo, Sangmin 22 Oct '15

22 Oct '15

The MPICH team will have a series of events at SC ’15 (http://sc15.supercomputing.org) including tutorials, talks, posters, BoFs, and demos. Come and meet us at the following events: Tutorials - Nov. 15 (Sun) / 08:30am – 05:00pm / 12A / Parallel I/O In Practice - Nov. 16 (Mon) / 08:30am – 05:00pm / 18B / Advanced MPI Programming Keynote speech - Nov. 16 (Mon) / Pavan Balaji @ ExaMPI Papers - Nov. 17 (Tue) / 04:00pm – 04:30pm / 18CD / Improving Concurrency and Asynchrony in Multithreaded MPI Applications using Software Offloading - Nov. 18 (Wed) / 11:30am – 12:00pm / 19AB / Fault Tolerant MapReduce-MPI for HPC Clusters - Nov. 19 (Thu) / 02:00pm – 02:30pm / 19AB / VOCL-FT: Introducing Techniques for Efficient Soft Error Coprocessor Recovery Posters - Nov. 17 (Tue) / 05:15pm – 07:00pm / Level 4 – Concourse / Argo: An Exascale Operating System and Runtime BoFs - Nov. 17 (Tue) / 05:30pm – 07:00pm / 17AB / MPICH: A High-Performance Open-Source MPI Implementation - Nov. 18 (Wed) / 03:30pm – 05:00pm / 15 / The Message Passing Interface: MPI 3.1 Released, Next Stop MPI 4.0 - Nov. 18 (Wed) / 05:30pm – 07:00pm / 19AB / Towards Standardized, Portable and Lightweight User-Level Threads and Tasks Demos/Presentations - DOE Booth: Argo demo/presentation (TBD) For links and updated information for all events, please visit http://www.mpich.org/2015/10/15/meet-us-at-sc-15/ We are looking forward to seeing you at SC '15. Regards, The MPICH Team _______________________________________________ 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] problem after compilation
by vinod pandey 22 Oct '15

22 Oct '15

I have followed the instructions while building and installing mpich. I didnt face any problem in that part. Its just after compilation that this error message occurs. Vinod On Fri, Oct 23, 2015 at 12:19 AM, Balaji, Pavan <balaji(a)anl.gov> wrote: > > It's best to go through the README for step-by-step instructions on how to > build mpich. > > -- Pavan > > From: vinod pandey <pandeyvinod4(a)gmail.com> > Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Date: Thursday, October 22, 2015 at 1:37 PM > To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Subject: Re: [mpich-discuss] problem after compilation > > Thanks for the reply but I am completely new to it. Can you please suggest > me what exactly I can do to avoid this error. > thanks and regards. > > On Thu, Oct 22, 2015 at 8:57 PM, Balaji, Pavan <balaji(a)anl.gov> wrote: > >> >> You seem to be mixing MPICH and a different MPI implementation (probably >> Open MPI). >> >> From: vinod pandey <pandeyvinod4(a)gmail.com> >> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> >> Date: Thursday, October 22, 2015 at 2:30 AM >> To: "discuss(a)mpich.org" <discuss(a)mpich.org> >> Subject: [mpich-discuss] problem after compilation >> >> I am getting the below message after compilation >> >> /usr/bin/ld: warning: libmpi.so.1, needed by /usr//lib/libmpi_f77.so, may >> conflict with libmpi.so.12 >> >> Kindly help. >> -- >> ............. >> VINOD PANDEY >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > > > -- > ............. > VINOD PANDEY > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- ............. VINOD PANDEY _______________________________________________ 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] problem after compilation
by Balaji, Pavan 22 Oct '15

22 Oct '15

It's best to go through the README for step-by-step instructions on how to build mpich. -- Pavan From: vinod pandey <pandeyvinod4(a)gmail.com<mailto:[email protected]>> Reply-To: "discuss(a)mpich.org<mailto:[email protected]>" <discuss(a)mpich.org<mailto:[email protected]>> Date: Thursday, October 22, 2015 at 1:37 PM To: "discuss(a)mpich.org<mailto:[email protected]>" <discuss(a)mpich.org<mailto:[email protected]>> Subject: Re: [mpich-discuss] problem after compilation Thanks for the reply but I am completely new to it. Can you please suggest me what exactly I can do to avoid this error. thanks and regards. On Thu, Oct 22, 2015 at 8:57 PM, Balaji, Pavan <balaji(a)anl.gov<mailto:[email protected]>> wrote: You seem to be mixing MPICH and a different MPI implementation (probably Open MPI). From: vinod pandey <pandeyvinod4(a)gmail.com<mailto:[email protected]>> Reply-To: "discuss(a)mpich.org<mailto:[email protected]>" <discuss(a)mpich.org<mailto:[email protected]>> Date: Thursday, October 22, 2015 at 2:30 AM To: "discuss(a)mpich.org<mailto:[email protected]>" <discuss(a)mpich.org<mailto:[email protected]>> Subject: [mpich-discuss] problem after compilation I am getting the below message after compilation /usr/bin/ld: warning: libmpi.so.1, needed by /usr//lib/libmpi_f77.so, may conflict with libmpi.so.12 Kindly help. -- ............. VINOD PANDEY _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss -- ............. VINOD PANDEY _______________________________________________ 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] problem after compilation
by vinod pandey 22 Oct '15

22 Oct '15

Thanks for the reply but I am completely new to it. Can you please suggest me what exactly I can do to avoid this error. thanks and regards. On Thu, Oct 22, 2015 at 8:57 PM, Balaji, Pavan <balaji(a)anl.gov> wrote: > > You seem to be mixing MPICH and a different MPI implementation (probably > Open MPI). > > From: vinod pandey <pandeyvinod4(a)gmail.com> > Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Date: Thursday, October 22, 2015 at 2:30 AM > To: "discuss(a)mpich.org" <discuss(a)mpich.org> > Subject: [mpich-discuss] problem after compilation > > I am getting the below message after compilation > > /usr/bin/ld: warning: libmpi.so.1, needed by /usr//lib/libmpi_f77.so, may > conflict with libmpi.so.12 > > Kindly help. > -- > ............. > VINOD PANDEY > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- ............. VINOD PANDEY _______________________________________________ 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] Questions about non-blocking collective calls...
by Balaji, Pavan 22 Oct '15

22 Oct '15

Eric, I'm not sure I understand your question. MPI assumes smart users. :-) If there's something you can do on top of MPI, with the same efficiency as within MPI, then we typically avoid adding it into the standard and assume that the users will do it on their own, or more likely that someone will provide a higher-level library above MPI to do that for you. There are some exceptions to this rule, of course (e.g., MPI_DIMS_CREATE, which is a widely used, but a useless part of the standard, IMO -- you can implement it above MPI), but I'm talking about the general trend. This particular case is no different. If you write this above MPI, in a portable way, you can get most but not all of the performance. For example, if MPI detects that your network is InfiniBand or Portals, it can use triggered collectives to do the same operation more efficiently. It can internally use shared memory in some cases. It can internally hardware offload the communication, if the network switch supports it. As both Jeff and I pointed out -- you'll get most of the performance doing this above MPI, so you might not care about the last 10% that you might lose. But it is in the standard for people who care about that level of performance. Another side-effect that you might not consider is that of progress. If you do this above MPI, if you are blocked inside a different MPI call (say you called some other library like PETSc, which did an MPI barrier), you are not making progress on your home-grown collective. If this is integrated into MPI, the MPI library will make progress for you. In any case, I think we have gone beyond MPICH and into the MPI standard territory. So maybe this discussion is best to have on the Forum mailing list. You can find more information here: http://meetings.mpi-forum.org/MPI_4.0_main_page.php -- Pavan On 10/22/15, 12:29 PM, "Eric Chamberland" <Eric.Chamberland(a)giref.ulaval.ca> wrote: >Hi Pavan and Jeff, > >Thanks a lot for your answers. > >I feel there is something to tell about mpi standard expectations... > >Why does the knowledge (or ignorance) of MPI users about scalability of >communications in MPI should be a requirement for them for developing >high-performance MPI applications? Especially when we want to keep it >simple by using high-level MPI functionalities, like MPI_gather, and let >the library do the best work it can... > >In other words, why the complexity (then scalability) of MPI algorithms >is not guaranteed by the standard? If every one that is familiar with >performance of MPI communication have the burden to write MPI calls in a >way that it is scaling/performing well, isn't all of us rewriting >essentially the same "good" code that should be in the standard? > >Is the standard voluntarily blind to these (crucial) questions? > >I may be too naive too... tell me! :) > >(ie, the c++ standard guarantee the sort algorithm complexity: >https://en.wikipedia.org/wiki/Sort_%28C%2B%2B%29) > >On 21/10/15 10:03 PM, Balaji, Pavan wrote: > > You might want to join the collectives working group and voice your >opinion over there. > >Ok, where exactly do I do this? > >Btw, I don't want to blame anybody... I am just learning and discussing >here!!! :) > >Thanks for reading! > >Eric > >On 21/10/15 11:56 PM, Jeff Hammond wrote: >> Depending on the size of your data, you could pipeline a series of >> MPI_Igather calls and process all of the data associated with the >> partial buffer. Of course, this will change the layout of the buffer at >> the root unless you do something interesting with datatypes (e.g. struct >> with offset). This may or may not matter, if you are going to process >> it anyways. >> >> In general, I think you may be able to do just fine with rolling your >> own. It's a myth that using higher-level functionality in MPI is >> _always_ better. >> >> Jeff >> >> On Wed, Oct 21, 2015 at 7:03 PM, Balaji, Pavan <balaji(a)anl.gov >> <mailto:[email protected]>> wrote: >> >> Eric, >> >> The concept of partial completion of collectives did come up in the >> Forum, but the Forum decided that it was rather unnatural to define >> Iallgather/Igather that way. So we decided to standardize it the >> way it is. >> >> However, there is a separate proposal for streaming collectives, >> which is more along the lines of what you are thinking of. That's >> obviously not in MPI-3, but might be considered for a future MPI. >> You might want to join the collectives working group and voice your >> opinion over there. >> >> With respect to writing your own igather implementation, as long as >> your implementation is logarithmic, it won't be too bad. However, a >> native implementation inside MPI would almost certainly do better >> because: (1) it can take advantage of platform-specific features to >> improve performance, and (2) if the platform doesn't give anything >> special, it'll anyway do exactly what you are doing above MPI. >> >> So, apart from any performance bugs that the implementation might >> have, using MPI Igather would be the recommended mechanism for the >> best performance. >> >> -- Pavan >> >> >> >> >> >> On 10/21/15, 2:45 PM, "Eric Chamberland" >> <Eric.Chamberland(a)giref.ulaval.ca >> <mailto:[email protected]>> wrote: >> >> >Hi, >> > >> >A long time ago (in 2002) we programmed here a non-blocking >> MPI_Igather >> >with equivalent calls to MPI_Isend/MPI_Irecv (see the 2 attached >> files). >> > >> >A very convenient advantage of this version, is that I can do some >> work >> >on the root process as soon as it start receiving data... Then, >> it wait >> >for the next communication to terminate and process the received data. >> > >> >Now, I am looking at MPI_Igather (and all non-blocking collective MPI >> >calls), and I am somewhat surprised (or ignorant) that I cannot >> have the >> >root rank receive some data, then process it, then wait until the next >> >"MPI_irecv" terminate... >> > >> >In other words, a MPI_Igather generate only 1 MPI_Request but I would >> >like to have either "p" (with p = size of communicator) MPI_Request >> >generated or be able to call "p" times MPI_WaitAny with the same >> >MPI_Request... Am I normal? :) >> > >> >So my 3 questions are: >> > >> >#1- Is there a way to use MPI_Igather with MPI_WaitAny (or something >> >else?) to process data as it is received? >> > >> >#2- Big question: will our implementation with MPI_Isend/MPI_Irecv >> scale >> >to a large number of processes? What are the possible drawbacks of >> >doing it like we did? >> > >> >#3- Why should I replace our implementation by the native MPI_Igather? >> > >> >Thanks! >> > >> >Eric >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com <mailto:[email protected]> >> http://jeffhammond.github.io/ > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0