[MPIWG Fortran] Draft chapter for discussion today

Fri Jan 17 08:32:30 CST 2014

Dear Jeff,

the content is okay, but I have a few issues with a 
missing completeness of the ticket:

- MPI-3.0, in Table 2.1, after p18:34 add:

    mpif.h (5)  [deprecated since] MPI-4.0  [Replacement] mpi or mpi_f08 module

  and after p18:37:

    (5) Include file.

- The whole text of section 17.1.4 must be moved into the new

    15.3 Deprecated since MPI-4.0

    15.3.1 Fortran Support through the mpif.h Include File

        With MPI-4.0, the Section 17.1.4 on page ... 
        was deprecated and moved into this Section 15.3.1.

        [Old text from 17.1.4 with the proposed modifications.]
        The use of the mpif.h include file is deprecated and may be
        deleted from a future Version of MPI.
        ...

    17.1.4 Fortran Support through the mpif.h Include File

        Since MPI-4.0, the use of the mpif.h include file is deprecated 
        and the content of this section was moved into Section 15.3.1 on page ... .

- MPI-3.0 p11:17 reads

>   The Fortran version of the same function used 
>   with USE mpi or INCLUDE 'mpif.h'.

  but should read

    And additionally for routines that existed already in MPI-3.0:
>   The Fortran version of the same function used 
>   with USE mpi 
    or the deprecated 
>   INCLUDE 'mpif.h'.

- MPI-3.0 p12:40, p30:19 reads

    INCLUDE 'mpif.h'

  but should read

    the deprecated INCLUDE 'mpif.h'

- MPI-3.0 p13:21 reads

    mpif.h or the mpi module

  but should read

    the mpi module or the deprecated mpif.h

- MPI-3.0 p16:19 reads

    the include file mpif.h or the mpi module

  but should read

    the mpi module or the deprecated include file mpif.h

- MPI-3.0 p19:19 reads

    mpif.h and use mpi

  but should read

    use mpi and the deprecated mpif.h

- MPI-3.0 p32:18 reads

>   mpi.h and mpif.h

  but should read

    mpi.h, the Fortran modules mpi_f08 and mpi, and in the deprecated mpif.h

- MPI-3.0 p45:36, p268:38, p270:10, p270:21, p274:14, p277:26, p339:45, 
          p344:26, p346:16, p347:40, p407:48, p409:31, p411:12,
          p475:15, p475:47, p476:42, 680:36, p680:37 reads

    mpif.h

  but should read

    the deprecated mpif.h

- MPI-3.0 p367:16, p379:48 reads

    the include file mpif.h

  but should read

    the deprecated include file mpif.h

- MPI-3.0 p545:14 reads

    the mpif.h

  but should read

    the deprecated mpif.h

- MPI-3.0 p605-659 (Fortran Chapter, starting with 17.1.5) reads

    mpif.h

  but should read

    the deprecated mpif.h

- MPI-3.0 p756:1 reads

    Fortran Bindings with mpif.h or the mpi Module

  but should read (would be too Long with "deprecated")

    Fortran Bindings with the mpi Module or mpif.h

I do not expect that I found all issues, but at least some ;-)

Best regards
Rolf

----- Original Message -----
> From: "Jeff Squyres (jsquyres)" <jsquyres at cisco.com>
> To: "MPI-WG Fortran working group" <mpiwg-fortran at lists.mpi-forum.org>
> Sent: Thursday, January 16, 2014 8:13:06 PM
> Subject: Re: [MPIWG Fortran] Draft chapter for discussion today
> 
> We tweaked the document a bit more on the call; here's the final
> result.
> 
>
> On Jan 16, 2014, at 11:18 AM, "Jeff Squyres (jsquyres)"
> <jsquyres at cisco.com>
>  wrote:
> 
> > Sure -- we're starting in about 40 minutes (noon, US Eastern time).
> > 
> > Here's the content from the invite:
> > 
> > The main point of this meeting is to discuss 2 MPI-4 proposals that
> > Jeff will have ready:
> > 
> > 1. Deprecate mpif.h.  Rolf's suggestion:
> > 
> > MPI-3 p603, chap 17.1.4
> > 1st para -- "mpif.h is strongly discouraged and may be
> > deprecated..."
> >  --> change to "is deprecated and may be deleted..."
> >  --> Add (short) AtoU, if you have software using mpif.h, you
> >should
> >      change it thusly...  (see page 603 line 15-17 for
> >      inspiration/copy)
> > 
> > 2. Freeze the mpi module (no new features).  The intent is to focus
> > all of our energies on the mpi_f08 module in the future.  If there
> > is push back on this from the Forum, our plan B for this is to
> > modernize the mpi module (i.e., add all the features to the mpi
> > module that we added to the mpi_f08 module).  Rolf's suggestions:
> > 
> > --> Add AtoU encourage users to move to mpi_f08
> > 
> > --------
> > 
> > **** You can forward this email invitation to attendees ****
> > 
> > Hello ,
> > 
> > Jeff Squyres invites you to attend this online meeting.
> > 
> > Topic: MPI Forum Fortran WG
> > Date: Thursday, January 16, 2014
> > Time: 12:00 pm, Eastern Standard Time (New York, GMT-05:00)
> > Meeting Number: 203 787 876
> > Meeting Password: mpi
> > 
> > 
> > -------------------------------------------------------
> > To join the online meeting (Now from mobile devices!)
> > -------------------------------------------------------
> > 1. Go to
> > https://cisco.webex.com/ciscosales/j.php?ED=248676957&UID=0&PW=NY2UzZmNiNWY3&RT=MiMxMQ%3D%3D
> > 2. Enter your name and email address.
> > 3. Enter the meeting password: mpi
> > 4. Click "Join Now".
> > 
> > To view in other time zones or languages, please click the link:
> > https://cisco.webex.com/ciscosales/j.php?ED=248676957&UID=0&PW=NY2UzZmNiNWY3&ORT=MiMxMQ%3D%3D
> > 
> > ----------------------------------------------------------------
> > ALERT – PLEASE READ: DO NOT DIAL THE TOLL FREE NUMBERS FROM WITHIN
> > THE (408) OR (919) AREA CODES
> > ----------------------------------------------------------------
> > Please dial the local access number for your area from the list
> > below:
> > - San Jose/Milpitas (408) area: 525-6800
> > - RTP (919) area: 392-3330
> > 
> > Dialing the WebEx toll free numbers from within 408 or 919 area
> > codes is not enabled (non-Cisco phones). “ If you dial the
> > toll-free numbers within the 408 or 919 area codes you will be
> > instructed to hang up and dial the local access number.” Please
> > use the call-back option whenever possible and otherwise dial
> > local numbers only. The affected toll free numbers are: (866)
> > 432-9903 for the San Jose/Milpitas area and (866) 349-3520 for the
> > RTP area.
> > 
> > -------------------------------------------------------
> > To join the teleconference only
> > -------------------------------------------------------
> > 1. Dial into Cisco WebEx (view all Global Access Numbers at
> > http://cisco.com/en/US/about/doing_business/conferencing/index.html
> > 2. Follow the prompts to enter the Meeting Number (listed above) or
> > Access Code followed by the # sign.
> > 
> > San Jose, CA: +1.408.525.6800 RTP: +1.919.392.3330
> > 
> > US/Canada: +1.866.432.9903 United Kingdom: +44.20.8824.0117
> > 
> > India: +91.80.4350.1111 Germany: +49.619.6773.9002
> > 
> > Japan: +81.3.5763.9394 China: +86.10.8515.5666
> > 
> > -------------------------------------------------------
> > For assistance
> > -------------------------------------------------------
> > 1. Go to https://cisco.webex.com/ciscosales/mc
> > 2. On the left navigation bar, click "Support".
> > 
> > You can contact me at:
> > jsquyres at cisco.com
> > 1-408-525 0971
> > 
> > To add this meeting to your calendar program (for example Microsoft
> > Outlook), click this link:
> > https://cisco.webex.com/ciscosales/j.php?ED=248676957&UID=0&ICS=MI&LD=1&RD=2&ST=1&SHA2=AAAAAmq524Xr8fSGIfklv5EW9qFpNjnZuGzsEZOppDaCchyJ&RT=MiMxMQ%3D%3D
> > 
> > The playback of UCF (Universal Communications Format) rich media
> > files requires appropriate players. To view this type of rich
> > media files in the meeting, please check whether you have the
> > players installed on your computer by going to
> > https://cisco.webex.com/ciscosales/systemdiagnosis.php .
> > 
> > 
> > 
> > 
> > http://www.webex.com
> > 
> > CCP:+14085256800x203787876#
> > 
> > IMPORTANT NOTICE: This WebEx service includes a feature that allows
> > audio and any documents and other materials exchanged or viewed
> > during the session to be recorded. By joining this session, you
> > automatically consent to such recordings. If you do not consent to
> > the recording, discuss your concerns with the meeting host prior
> > to the start of the recording or do not join the session. Please
> > note that any such recordings may be subject to discovery in the
> > event of litigation.
> > 
> > 
> > 
> > 
> > 
> > 
> > On Jan 16, 2014, at 11:01 AM, Bill Long <longb at cray.com>
> > wrote:
> > 
> >> Hi Jeff,
> >> 
> >> Just starting another meeting.  Hopefully I’ll be out in time. 
> >> Before them, could you resend the webex link - I got a new
> >> computer at work with software that seems to delete the email
> >> message if you “accept” a meeting.
> >> 
> >> Cheers,
> >> Bill
> >> 
> >> 
> >> On Jan 16, 2014, at 9:03 AM, Jeff Squyres (jsquyres)
> >> <jsquyres at cisco.com> wrote:
> >> 
> >>> Here is a first cut of the language bindings chapter with changes
> >>> to:
> >>> 
> >>> 1. deprecate mpif.h
> >>> 2. freeze the mpi module
> >>> 
> >>> Look for "ticketWG" to see the changes -- I used the standard MPI
> >>> update/replace macros, so all the changes are easily located. 
> >>> We'll talk through this text on the webex today.  The intent is
> >>> to introduce a ticket (or two?) at the next meeting for 1. and
> >>> 2.
> >>> 
> >>> Note that this PDF does *NOT* reflect the recently-passed tickets
> >>> for fixing the "linker name" language, etc.  This PDF draft for
> >>> discussion on the webex today is simply the MPI-3.0 text with my
> >>> updates for 1. and 2.
> >>> 
> >>> Updating the MPI-3.1 directory in SVN to include the text from
> >>> the recent tickets will be a separate effort.
> >>> 
> >>> --
> >>> Jeff Squyres
> >>> jsquyres at cisco.com
> >>> For corporate legal information go to:
> >>> http://www.cisco.com/web/about/doing_business/legal/cri/
> >>> <binding-2.pdf>_______________________________________________
> >>> mpiwg-fortran mailing list
> >>> mpiwg-fortran at lists.mpi-forum.org
> >>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
> >> 
> >> Bill
> >> Long                                                                      
> >> longb at cray.com
> >> Fortran Technical Suport  &                                 
> >> voice:  651-605-9024
> >> Bioinformatics Software Development                     fax: 
> >> 651-605-9142
> >> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN
> >> 55101
> >> 
> >> 
> >> _______________________________________________
> >> mpiwg-fortran mailing list
> >> mpiwg-fortran at lists.mpi-forum.org
> >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
> > 
> > 
> > --
> > Jeff Squyres
> > jsquyres at cisco.com
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/
> > 
> > _______________________________________________
> > mpiwg-fortran mailing list
> > mpiwg-fortran at lists.mpi-forum.org
> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran
> 
> 
> --
> Jeff Squyres
> jsquyres at cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> 
> _______________________________________________
> mpiwg-fortran mailing list
> mpiwg-fortran at lists.mpi-forum.org
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-fortran

-- 
Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner at 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: Room 1.307)