July 2012 - mpi-forum - mailman3.cels.anl.gov

Re: [Mpi-forum] Chapter Reviews
by Supalov, Alexander 20 Jul '12

20 Jul '12

Hi Rolf, There was an email from Darius - I took it. Best regards. Alexander -----Original Message----- From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Rolf Rabenseifner Sent: Friday, July 20, 2012 9:43 AM To: Main MPI Forum mailing list Subject: Re: [Mpi-forum] Chapter Reviews Alexander, thanks for the review. Which pdf (URL) was the basis? > Compliant MPI-3 implementations providing a Fortran interface must > provide provide one or both of the following: > _ The USE mpi_f08 Fortran support method. > _ The USE mpi and INCLUDE 'mpif.h' Fortran support methods. This sentence is based on the MPI-2.2 p480:44-46 statement: A compliant MPI-2 implementation providing a Fortran interface must provide Extended Fortran Support unless the target compiler does not support modules or KIND-parameterized types. It clearly allows also to "not provide" a Fortran interface. We added to this optional mpif.h + mpi module a new additional optional interface: the mpi_f08 module. Both mpich2 and OpenMPI have committed to provide mpi_f08, therefore there is not a real problem. There are other MPI's arround that never provided any Fortran support. Also okay. It was heavily discussed at the meetings and the current text is the democratic result. Best regards Rolf ----- Original Message ----- > From: "Alexander Supalov" <alexander.supalov(a)intel.com> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Friday, July 20, 2012 7:28:54 AM > Subject: Re: [Mpi-forum] Chapter Reviews Done (see attached). What is > the procedure to vet and implement these changes? > > > > By the way, whoever is going to review chapter 17, please look into > 602/1-6: > > > > Compliant MPI-3 implementations providing a Fortran interface must > provide provide > > one or both of the following: > > _ The USE mpi_f08 Fortran support method. > > _ The USE mpi and INCLUDE 'mpif.h' Fortran support methods. > > > > Double “provide” aside, this passage amounts to opening the door to a > silent removal (not even deprecation) of the old Fortran interface. > This cannot be the real intent of the Forum, I hope. Also, some > advices to the implementors effectively suggest breaking backward > compatibility on the old Fortran interface, if retained, up to and > including a failed application build and changes to the application > necessary as a consequence. Again, I think this is a bit too much of a > good thing. > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Richard > Graham > Sent: Thursday, July 19, 2012 5:29 PM > To: Main MPI Forum mailing list > Subject: Re: [Mpi-forum] Chapter Reviews > > > > Feel free to take it – thanks !!!! > > > > Rich > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Supalov, > Alexander > Sent: Thursday, July 19, 2012 11:02 AM > To: Main MPI Forum mailing list > Subject: Re: [Mpi-forum] Chapter Reviews > > > > Hi Rich, > > > > It might help those interested if you described the applicable > deadlines, the desired output of the review, and the resp. correction > procedure, should it become necessary. > > > > I hate to see my favorite Appendix A orphaned. Anyone against my > taking on it? > > > > Best regards. > > > > Alexander > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Richard > Graham > Sent: Thursday, July 19, 2012 4:45 PM > To: mpi-forum(a)lists.mpi-forum.org > Subject: [Mpi-forum] Chapter Reviews > > > > We are currently doing chapter reviews for the forum – all tickets are > committed and reviewed. If anyone has changes to make please > coordinate this morning (Thursday 7/19/2012 – Chicago time) with the > person who is doing the review. After these are done, responsibility > will revert to the chapter committees. I will send out a separate > note on the timelines we agreed to yesterday, but in a nutshell, all > changes must be completed and reviewed by Thursday 7/26/2012, 5pm > Pacific time, so that we can prepare a draft version to be posted for > comment. > > > > If someone remote would like to take the responsibility for an > unclaimed chapter, please let me know. > > > > Thanks, > > Rich > > > > Chapter Reviewer > > Front Matter Mohamad > > Chap 1 Brian B. > > Chap 2 Scott > > Chap 3 Anh > > Chap 4 Terry > > Chap 5 Nathan > > Chap 6 Darius > > Chap 7 Shinji > > Chap 8 Pavan > > Chap 9 Howard - done > > Chap 10 Hideyuki > > Chap 11 Howard > > Chap 12 Brian S. > > Chap 13 Brian S. > > Chap 14 Rich > > Chap 15 > > Chap 16 > > Chap 17 > > Appendix A > > Appendix B Jeff/Rolf > > Bib > > Indices > > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: > Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, > Christian Lamprechter > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. > (BLZ 502 109 00) 600119052 Intel GmbH Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: > Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, > Christian Lamprechter > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. > (BLZ 502 109 00) 600119052 > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30) _______________________________________________ mpi-forum mailing list mpi-forum(a)lists.mpi-forum.org http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, Christian Lamprechter Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Re: [Mpi-forum] Chapter Reviews
by Rolf Rabenseifner 20 Jul '12

20 Jul '12

Alexander, thanks for the review. Which pdf (URL) was the basis? > Compliant MPI-3 implementations providing a Fortran interface must > provide provide one or both of the following: > _ The USE mpi_f08 Fortran support method. > _ The USE mpi and INCLUDE 'mpif.h' Fortran support methods. This sentence is based on the MPI-2.2 p480:44-46 statement: A compliant MPI-2 implementation providing a Fortran interface must provide Extended Fortran Support unless the target compiler does not support modules or KIND-parameterized types. It clearly allows also to "not provide" a Fortran interface. We added to this optional mpif.h + mpi module a new additional optional interface: the mpi_f08 module. Both mpich2 and OpenMPI have committed to provide mpi_f08, therefore there is not a real problem. There are other MPI's arround that never provided any Fortran support. Also okay. It was heavily discussed at the meetings and the current text is the democratic result. Best regards Rolf ----- Original Message ----- > From: "Alexander Supalov" <alexander.supalov(a)intel.com> > To: "Main MPI Forum mailing list" <mpi-forum(a)lists.mpi-forum.org> > Sent: Friday, July 20, 2012 7:28:54 AM > Subject: Re: [Mpi-forum] Chapter Reviews > Done (see attached). What is the procedure to vet and implement these > changes? > > > > By the way, whoever is going to review chapter 17, please look into > 602/1-6: > > > > Compliant MPI-3 implementations providing a Fortran interface must > provide provide > > one or both of the following: > > _ The USE mpi_f08 Fortran support method. > > _ The USE mpi and INCLUDE 'mpif.h' Fortran support methods. > > > > Double “provide” aside, this passage amounts to opening the door to a > silent removal (not even deprecation) of the old Fortran interface. > This cannot be the real intent of the Forum, I hope. Also, some > advices to the implementors effectively suggest breaking backward > compatibility on the old Fortran interface, if retained, up to and > including a failed application build and changes to the application > necessary as a consequence. Again, I think this is a bit too much of a > good thing. > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Richard > Graham > Sent: Thursday, July 19, 2012 5:29 PM > To: Main MPI Forum mailing list > Subject: Re: [Mpi-forum] Chapter Reviews > > > > Feel free to take it – thanks !!!! > > > > Rich > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Supalov, > Alexander > Sent: Thursday, July 19, 2012 11:02 AM > To: Main MPI Forum mailing list > Subject: Re: [Mpi-forum] Chapter Reviews > > > > Hi Rich, > > > > It might help those interested if you described the applicable > deadlines, the desired output of the review, and the resp. correction > procedure, should it become necessary. > > > > I hate to see my favorite Appendix A orphaned. Anyone against my > taking on it? > > > > Best regards. > > > > Alexander > > > > > > From: mpi-forum-bounces(a)lists.mpi-forum.org > [mailto:[email protected]] On Behalf Of Richard > Graham > Sent: Thursday, July 19, 2012 4:45 PM > To: mpi-forum(a)lists.mpi-forum.org > Subject: [Mpi-forum] Chapter Reviews > > > > We are currently doing chapter reviews for the forum – all tickets are > committed and reviewed. If anyone has changes to make please > coordinate this morning (Thursday 7/19/2012 – Chicago time) with the > person who is doing the review. After these are done, responsibility > will revert to the chapter committees. I will send out a separate > note on the timelines we agreed to yesterday, but in a nutshell, all > changes must be completed and reviewed by Thursday 7/26/2012, 5pm > Pacific time, so that we can prepare a draft version to be posted for > comment. > > > > If someone remote would like to take the responsibility for an > unclaimed chapter, please let me know. > > > > Thanks, > > Rich > > > > Chapter Reviewer > > Front Matter Mohamad > > Chap 1 Brian B. > > Chap 2 Scott > > Chap 3 Anh > > Chap 4 Terry > > Chap 5 Nathan > > Chap 6 Darius > > Chap 7 Shinji > > Chap 8 Pavan > > Chap 9 Howard - done > > Chap 10 Hideyuki > > Chap 11 Howard > > Chap 12 Brian S. > > Chap 13 Brian S. > > Chap 14 Rich > > Chap 15 > > Chap 16 > > Chap 17 > > Appendix A > > Appendix B Jeff/Rolf > > Bib > > Indices > > Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, > Christian Lamprechter > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 > Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 Intel GmbH > Dornacher Strasse 1 > 85622 Feldkirchen/Muenchen, Deutschland > Sitz der Gesellschaft: Feldkirchen bei Muenchen > Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, > Christian Lamprechter > Registergericht: Muenchen HRB 47456 > Ust.-IdNr./VAT Registration No.: DE129385895 > Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum -- Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner(a)hlrs.de High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530 University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832 Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)

1 0

Re: [Mpi-forum] Sept MPI Forum meeting
by Jesper Larsson Träff 20 Jul '12

20 Jul '12

Hi all, Rich requested the week before EuroMPI looong time ago (for 4 days), and we have found room etc. for that period. After EuroMPI is close to semester start here in Austria, that is, it will be much more difficult now to get a seminar room for that period. Of course, the overlap with PaCT is very unfortunate (and these overlaps are often a problem for EuroMPI - something we could discuss at the "Business Meeting" at the conference!) All I wanted to say is: please make up your mind soon and let us know what we should plan for Best, Jesper On Thu, Jul 19, 2012 at 07:21:34PM +0200, Torsten Hoefler wrote: > Rich, > > That sounds fine. The current dates overlap 100% with PACT, which > prevents me from attending the MPI Forum. I would appreciate to have it > after EuroMPI. But I understand if other reasons disallow a > re-scheduling or if it's to late to make such a change. I just thought > I'd bring this conflict up :-). > > Thanks, > Torsten > > On Wed, 2012-07-18 at 23:17 +0000, Richard Graham wrote: > > In the meeting today, we discussed changing the schedule for the Sept > > meeting in Vienna. Since we are at a transition stage between MPI 3.0 > > and “MPI-next”, we decided to reduce the meetings from a 3 day meeting > > to a 2 day meeting - Sept 20-21, 2012. If someone knows of a reason > > to go back to a three day agenda, please let us know ASAP. The > > proposed agenda includes: > > > > > > > > Thursday – Sept 20th > > > > **************** > > > > 9-10 : Discussion of outside comments on the MPI 3.0 draft > > > > 10-12 : MPI 3.0: chapter votes > > > > 12-1 : lunch > > > > 1-5 : MPI-Next: organizational structure and areas of focus > > > > > > > > Friday – Sept 21 > > > > ************ > > > > 9-9:30 : MPI 3.0 - final vote > > > > 9:30 -12 : Working group time > > > > 12-1 lunch > > > > 1-3 : Working group time > > > > 3-5 : MPI-Next: organizational structure and areas of focus – cont’d > > > > > > > > If there are other topics that should be added to the agenda, please > > let me know ASAP. > > > > > > > > Thanks, > > > > Rich > > > > > > > > > > > > > > > > _______________________________________________ > > mpi-forum mailing list > > mpi-forum(a)lists.mpi-forum.org > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > >

1 0

Re: [Mpi-forum] Chapter Reviews
by Supalov, Alexander 20 Jul '12

20 Jul '12

Done (see attached). What is the procedure to vet and implement these changes? By the way, whoever is going to review chapter 17, please look into 602/1-6: Compliant MPI-3 implementations providing a Fortran interface must provide provide one or both of the following: _ The USE mpi_f08 Fortran support method. _ The USE mpi and INCLUDE 'mpif.h' Fortran support methods. Double "provide" aside, this passage amounts to opening the door to a silent removal (not even deprecation) of the old Fortran interface. This cannot be the real intent of the Forum, I hope. Also, some advices to the implementors effectively suggest breaking backward compatibility on the old Fortran interface, if retained, up to and including a failed application build and changes to the application necessary as a consequence. Again, I think this is a bit too much of a good thing. From: mpi-forum-bounces(a)lists.mpi-forum.org [mailto:[email protected]] On Behalf Of Richard Graham Sent: Thursday, July 19, 2012 5:29 PM To: Main MPI Forum mailing list Subject: Re: [Mpi-forum] Chapter Reviews Feel free to take it - thanks !!!! Rich From: mpi-forum-bounces(a)lists.mpi-forum.org<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Supalov, Alexander Sent: Thursday, July 19, 2012 11:02 AM To: Main MPI Forum mailing list Subject: Re: [Mpi-forum] Chapter Reviews Hi Rich, It might help those interested if you described the applicable deadlines, the desired output of the review, and the resp. correction procedure, should it become necessary. I hate to see my favorite Appendix A orphaned. Anyone against my taking on it? Best regards. Alexander From: mpi-forum-bounces(a)lists.mpi-forum.org<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Richard Graham Sent: Thursday, July 19, 2012 4:45 PM To: mpi-forum(a)lists.mpi-forum.org<mailto:[email protected]> Subject: [Mpi-forum] Chapter Reviews We are currently doing chapter reviews for the forum - all tickets are committed and reviewed. If anyone has changes to make please coordinate this morning (Thursday 7/19/2012 - Chicago time) with the person who is doing the review. After these are done, responsibility will revert to the chapter committees. I will send out a separate note on the timelines we agreed to yesterday, but in a nutshell, all changes must be completed and reviewed by Thursday 7/26/2012, 5pm Pacific time, so that we can prepare a draft version to be posted for comment. If someone remote would like to take the responsibility for an unclaimed chapter, please let me know. Thanks, Rich Chapter Reviewer Front Matter Mohamad Chap 1 Brian B. Chap 2 Scott Chap 3 Anh Chap 4 Terry Chap 5 Nathan Chap 6 Darius Chap 7 Shinji Chap 8 Pavan Chap 9 Howard - done Chap 10 Hideyuki Chap 11 Howard Chap 12 Brian S. Chap 13 Brian S. Chap 14 Rich Chap 15 Chap 16 Chap 17 Appendix A Appendix B Jeff/Rolf Bib Indices Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, Christian Lamprechter Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer, Christian Lamprechter Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

1 0

Re: [Mpi-forum] Indices
by George Bosilca 19 Jul '12

19 Jul '12

Torsten, When the usage of the MPI_LB and MPI_UB has been replaced by the resize function the arrays used by the MPI_Type_struct (displacement and blacken) have been left behind. The patch below clean one of the examples from the collective chapter. george. Index: chap-coll/coll.tex =================================================================== --- chap-coll/coll.tex (revision 1482) +++ chap-coll/coll.tex (working copy) @@ -1212,14 +1211,15 @@ %%HEADER %%LANG: C %%FRAGMENT +%%SUBST:...: %%SKIPELIPSIS %%ENDHEADER \begin{Verbatim}[commandchars=\\\$\^] MPI_Comm comm; - int gsize,sendarray[100][150],*sptr; - int root, *rbuf, stride, myrank, disp[2], blocklen[2]; - MPI_Datatype stype,type[2]; - int *displs,i,*rcounts; + int gsize, sendarray[100][150], *sptr; + int root, *rbuf, stride, myrank; + MPI_Datatype stype; + int *displs, i, *rcounts; ... On Jul 19, 2012, at 20:21 , William Gropp wrote: > Yes, these need to be fixed. > > Mixed case in the function index means either the C binding name (or Fortran08 name) was used where the language-independent name should be used, or \func or \mpifunc were used for a language-binding-specific name (which is incorrect macro usage). Chapter authors need to fix this. There as also some non-functions in the function index; those must be fixed. > > Example index entries need to be checked; I added a bunch to context as many examples were missing the index entries (made with \exindex). > > I think it is ok for removed and deprecated names to show up in the index. > > Bill > > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > > > On Jul 19, 2012, at 12:17 PM, Mohamad Chaarawi wrote: > >> Hi All, >> >> After reviewing the indices, I found a few issues: >> >> - MPI_Type_struct and MPI_TYPE_EXTENT show up in the example indices. This should not happen as they are removed. >> - I'm not sure if removed and deprecated routines should show up in the Function Index, but right now, they do. >> - similarly in the MPI Callback Function Prototype Index >> - similarly in Constant and Predefined Handle Index >> - in the function index, many routines show up twice (caps and no caps) and some show up only with no caps.. All should be caps (I think). >> >> Do the chapter authors need to fix those in their chapters? >> >> Thanks, >> Mohamad >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

Re: [Mpi-forum] Indices
by George Bosilca 19 Jul '12

19 Jul '12

Here is the patch for the collective chapter removing the MPI_Type_struct from the example index. george. Index: chap-coll/coll.tex =================================================================== --- chap-coll/coll.tex (revision 1482) +++ chap-coll/coll.tex (working copy) @@ -1163,7 +1163,6 @@ \begin{example} {\rm \label{coll-exF} \exindex{MPI\_Gatherv}% -\exindex{MPI\_Type\_struct}% \exindex{MPI\_Type\_create\_struct}% \exindex{MPI\_Type\_commit}% @@ -1329,7 +1329,6 @@ \label{coll-exH} \exindex{MPI\_Gather}% \exindex{MPI\_Gatherv}% -\exindex{MPI\_Type\_struct}% \exindex{MPI\_Type\_create\_struct}% \exindex{MPI\_Type\_commit}% @@ -3999,7 +3998,6 @@ \label{coll-exW} \exindex{MPI\_Op\_create}% \exindex{MPI\_Scan}% -\exindex{MPI\_Type\_struct}% \exindex{MPI\_Type\_create\_struct}% \exindex{MPI\_Type\_commit}% On Jul 19, 2012, at 20:21 , William Gropp wrote: > Yes, these need to be fixed. > > Mixed case in the function index means either the C binding name (or Fortran08 name) was used where the language-independent name should be used, or \func or \mpifunc were used for a language-binding-specific name (which is incorrect macro usage). Chapter authors need to fix this. There as also some non-functions in the function index; those must be fixed. > > Example index entries need to be checked; I added a bunch to context as many examples were missing the index entries (made with \exindex). > > I think it is ok for removed and deprecated names to show up in the index. > > Bill > > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > > > On Jul 19, 2012, at 12:17 PM, Mohamad Chaarawi wrote: > >> Hi All, >> >> After reviewing the indices, I found a few issues: >> >> - MPI_Type_struct and MPI_TYPE_EXTENT show up in the example indices. This should not happen as they are removed. >> - I'm not sure if removed and deprecated routines should show up in the Function Index, but right now, they do. >> - similarly in the MPI Callback Function Prototype Index >> - similarly in Constant and Predefined Handle Index >> - in the function index, many routines show up twice (caps and no caps) and some show up only with no caps.. All should be caps (I think). >> >> Do the chapter authors need to fix those in their chapters? >> >> Thanks, >> Mohamad >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

lots of undefined references
by Rajeev Thakur 19 Jul '12

19 Jul '12

This is with make cleandoc. LaTeX Warning: Reference `terms-cpp' on page 9 undefined on input line 64. LaTeX Warning: Reference `terms-cpp' on page 9 undefined on input line 64. LaTeX Warning: Reference `app:annex-c++-bindings' on page 22 undefined on input LaTeX Warning: Reference `sec:bindings-c++exceptions' on page 24 undefined on i LaTeX Warning: Reference `sec:bindings-c++exceptions' on page 24 undefined on i LaTeX Warning: Reference `c++comm-class' on page 246 undefined on input line 88 LaTeX Warning: Reference `c++comm-class' on page 246 undefined on input line 88 LaTeX Warning: Reference `sec:misc-addresses' on page 274 undefined on input li LaTeX Warning: Reference `poisson' on page 338 undefined on input line 2404. LaTeX Warning: Reference `sec:c++profile' on page 572 undefined on input line 3 LaTeX Warning: Reference `app:annex-c++-bindings' on page 622 undefined on inpu LaTeX Warning: Reference `tab:cpp-basic-datatypes' on page 625 undefined on inp LaTeX Warning: Reference `tab:fort-basic-datatypes' on page 625 undefined on in LaTeX Warning: Reference `tab:other-datatypes' on page 625 undefined on input l LaTeX Warning: Reference `sec:misc-c++interlanguage' on page 632 undefined on i LaTeX Warning: Reference `sec:c++datatypes' on page 831 undefined on input line LaTeX Warning: Reference `tab:cpp-basic-datatypes' on page 831 undefined on inp LaTeX Warning: Reference `tab:cpp-basic-datatypes' on page 831 undefined on inp LaTeX Warning: Reference `sec:c++datatypes' on page 832 undefined on input line LaTeX Warning: Reference `sec:c++datatypes' on page 832 undefined on input line LaTeX Warning: Reference `func:mpi-type-size-x' on page 833 undefined on input LaTeX Warning: Reference `func:mpi-type-get-extent-x' on page 833 undefined on LaTeX Warning: Reference `func:mpi-type-size-x' on page 833 undefined on input LaTeX Warning: Reference `func:mpi-type-get-extent-x' on page 833 undefined on LaTeX Warning: Reference `func:mpi-get-count' on page 833 undefined on input li LaTeX Warning: Reference `func:mpi-type-size' on page 833 undefined on input li LaTeX Warning: Reference `func:mpi-get-elements' on page 833 undefined on input LaTeX Warning: Reference `func:mpi-pack-size' on page 833 undefined on input li LaTeX Warning: Reference `func:mpi-get-count' on page 833 undefined on input li LaTeX Warning: Reference `func:mpi-type-size' on page 833 undefined on input li LaTeX Warning: Reference `func:mpi-get-elements' on page 833 undefined on input LaTeX Warning: Reference `func:mpi-pack-size' on page 833 undefined on input li LaTeX Warning: Reference `terms-cpp' on page 837 undefined on input line 851. LaTeX Warning: Reference `terms-cpp' on page 837 undefined on input line 851. LaTeX Warning: Reference `sec:cpp' on page 837 undefined on input line 852. LaTeX Warning: Reference `sec:cpp' on page 837 undefined on input line 852. LaTeX Warning: Reference `sec:c++datatypes' on page 839 undefined on input line LaTeX Warning: Reference `sec:c++datatypes' on page 839 undefined on input line LaTeX Warning: Reference `sec:c++datatypes' on page 839 undefined on input line LaTeX Warning: Reference `sec:c++datatypes' on page 839 undefined on input line LaTeX Warning: Reference `sec:c++ClassMemberFunctions' on page 843 undefined on LaTeX Warning: Reference `sec:c++ClassMemberFunctions' on page 843 undefined on LaTeX Warning: There were undefined references.

1 0

Re: [Mpi-forum] Indices
by William Gropp 19 Jul '12

19 Jul '12

Yes, these need to be fixed. Mixed case in the function index means either the C binding name (or Fortran08 name) was used where the language-independent name should be used, or \func or \mpifunc were used for a language-binding-specific name (which is incorrect macro usage). Chapter authors need to fix this. There as also some non-functions in the function index; those must be fixed. Example index entries need to be checked; I added a bunch to context as many examples were missing the index entries (made with \exindex). I think it is ok for removed and deprecated names to show up in the index. Bill William Gropp Director, Parallel Computing Institute Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign On Jul 19, 2012, at 12:17 PM, Mohamad Chaarawi wrote: > Hi All, > > After reviewing the indices, I found a few issues: > > - MPI_Type_struct and MPI_TYPE_EXTENT show up in the example indices. This should not happen as they are removed. > - I'm not sure if removed and deprecated routines should show up in the Function Index, but right now, they do. > - similarly in the MPI Callback Function Prototype Index > - similarly in Constant and Predefined Handle Index > - in the function index, many routines show up twice (caps and no caps) and some show up only with no caps.. All should be caps (I think). > > Do the chapter authors need to fix those in their chapters? > > Thanks, > Mohamad > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum

1 0

Re: [Mpi-forum] Add MPI_COMM_SPLIT_TYPE to Comm Info?
by Darius Buntinas 19 Jul '12

19 Jul '12

I've finished my changes to that chapter and returned the token to Bill, so I don't want to make any more changes now. Bill: let me know if you want me to make this change. -d On Jul 19, 2012, at 12:36 PM, Adam T. Moody wrote: > Hi Darius, > I think we want to include MPI_COMM_SPLIT_TYPE in the list of functions that apply an info object to a communicator in the communicator info section 6.4.4. This at first feels a little strange, since globally you end up with multiple communicators after the call. However, each process should end up belonging to at most one new comm, so the info would naturally apply to the comm the process belongs to. > -Adam >

1 0

Re: [Mpi-forum] Final document of the night
by Jim Dinan 19 Jul '12

19 Jul '12

The sentence introducing the participants doesn't parse (page xxix, line 7): The following list includes some of the active participants who attended MPI-3 Forum meetings and in the e-mail discussions of the errata items and are not mentioned above. New text (add participated and comma): The following list includes some of the active participants who attended MPI-3 Forum meetings and _participated_ in the e-mail discussions of the errata items_,_ and are not mentioned above. ~Jim. On 7/19/12 11:18 AM, William Gropp wrote: > Got it. I'll add it after I hear that there are no more changes. > > Bill > > William Gropp > Director, Parallel Computing Institute > Deputy Director for Research > Institute for Advanced Computing Applications and Technologies > Paul and Cynthia Saylor Professor of Computer Science > University of Illinois Urbana-Champaign > > > > On Jul 19, 2012, at 10:24 AM, Jeff Hammond wrote: > >> On Thu, Jul 19, 2012 at 9:12 AM, William Gropp <wgropp(a)illinois.edu> wrote: >>> I've updated the credits list - please check. >> >> Please add "Jed Brown" to the list of active participants credited. >> >> Thanks, >> >> Jeff >> >> -- >> Jeff Hammond >> Argonne Leadership Computing Facility >> University of Chicago Computation Institute >> jhammond(a)alcf.anl.gov / (630) 252-5381 >> http://www.linkedin.com/in/jeffhammond >> https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond >> _______________________________________________ >> mpi-forum mailing list >> mpi-forum(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum > > _______________________________________________ > mpi-forum mailing list > mpi-forum(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum >

1 0