[MPI3 Fortran] MPI_INIT issues

[Bill Long]

Well, the descriptions of these routines has a lot of 
"processor-dependent" noise because the method for executing a program 
could be "unexpected".  However, the normal, unix-like command line 
should behave normally.  In F08, essentially all programs are assumed 
parallel, so I don't see the argument for serial only.

 > cat commd.f90
program test
   integer :: nargs,i,rank
   character(100) :: arg

   me = this_image()-1
   nargs = command_argument_count()
   call get_command_argument (0,arg)
   print *, "Rank ",me," command name = ",trim(arg)
   do i=1,nargs
      call get_command_argument (i,arg)
      print *, "Rank ",me," arg ", i," = ",trim(arg)
   end do
end program test

 > ftn commd.f90
 > aprun -n4 ./a.out arg1 arg2
  Rank  1  command name = ./a.out
  Rank  1  arg  1  = arg1
  Rank  1  arg  2  = arg2
  Rank  0  command name = ./a.out
  Rank  2  command name = ./a.out
  Rank  3  command name = ./a.out
  Rank  2  arg  1  = arg1
  Rank  0  arg  1  = arg1
  Rank  2  arg  2  = arg2
  Rank  0  arg  2  = arg2
  Rank  3  arg  1  = arg1
  Rank  3  arg  2  = arg2
Application 10969216 resources: utime ~0s, stime ~2s

I would expect the same output whether the parallelism was native or 
MPI.  So, it seems like it might be a solution in search of a problem.

Cheers,
Bill



On 2/20/13 11:21 AM, Rolf Rabenseifner wrote:
> As fas as I see,
> the MPI routines guarantee to work on all MPI processes,
> whereas the Fortran routines are guaranteed only in a
> sequential program.
>
> If you are doing slides, then please show the Fortran routine
> functionality (e.g., the INOUT quality of  a length argument)
> and compare it to the proposed MPI routine.
> They should be identical (i.e. least surprise).
> This would help the audience to see that the interface is okay.
>
> Best regards
> Rolf
>
> ----- Original Message -----
>> From: "Bill Long" <longb at cray.com>
>> To: mpi3-fortran at lists.mpi-forum.org
>> Sent: Wednesday, February 20, 2013 6:17:46 PM
>> Subject: Re: [MPI3 Fortran] MPI_INIT issues
>> I found the proposed solution confusing. If the Fortran user wants to
>> call COMMAND_ARGUMENT_COUNT or GET_COMMAND_ARGUMENT, why not just do
>> that directly? I don't see a point to creating new functions starting
>> with MPI_ .
>>
>> Cheers,
>> Bill
>>
>>
>>
>> On 2/20/13 11:02 AM, Jeff Squyres (jsquyres) wrote:
>>> I see that Martin put us on the agenda to discuss the MPI_INIT
>>> Fortran issues (see
>>> https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/351): 9-10am US
>>> Central on Tuesday morning.
>>>
>>> Do we have any slides to discuss, or a plan, or ...?
>>>
>>> Who will be there? (I will)
>>>
>>
>> --
>> Bill Long longb at cray.com
>> Fortran Technical Support & voice: 651-605-9024
>> Bioinformatics Software Development fax: 651-605-9142
>> Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101
>>
>>
>> _______________________________________________
>> mpi3-fortran mailing list
>> mpi3-fortran at lists.mpi-forum.org
>> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi3-fortran
>

-- 
Bill Long                                           longb at cray.com
Fortran Technical Support    &                 voice: 651-605-9024
Bioinformatics Software Development            fax:   651-605-9142
Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101