Dear MPI forum members,

for the virtual meeting this week (June 7, 2023) the following readings and 
discussions are scheduled.
Some technical decisions are needed and it may be best to do these decisions as 
institutional staw votes
in an additional virtual meeting (e.g. next week), rather to do them ad hoc 
this week.

The topics are #705/PR822,  #710/PR823 with two options,  #676/PR824 or PR825.

Details:
__________________________
#705 Errata: Fortran has only compile-time constants    Rolf,Joseph
     Issue https://github.com/mpi-forum/mpi-issues/issues/705
           (together with https://github.com/mpi-forum/mpi-issues/issues/657   
Rolf, Jeff H.)
     PR    https://github.com/mpi-forum/mpi-standard/pull/822
     PDF
     
https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue705%2B657_PR822.pdf

This proposal seems to be already stable.

__________________________
#710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect    Rolf
     Issue https://github.com/mpi-forum/mpi-issues/issues/710
     PR    https://github.com/mpi-forum/mpi-standard/pull/823
     PDF   
https://github.com/mpi-forum/mpi-standard/files/11454896/mpi41-report_Issue710_PR823.pdf

There is severe critism about the current proposal in PR 823:

  "In this PR here, as far as I can see, the implementations are mainly 
affected if they
   incorrectly require that there must not be any inactive request handle using 
the given comm.
   Whether an MPI lib really internally frees the inactive handles or not,
   is mainly a question of having dangling handles or not."
  "Is there broad agreement that this is incorrect implementation behavior? I'm 
skeptical."

And therefore, there are two different solutions:
  - An advice to users, telling the consequences if they do not free inactive
    handles before calling MPI_Comm_disconnect or MPI_Session_finalize.
or
  - Automatically freeing them.

And furthermore:

  "Whatever we decide, I imagine this needs to extend to MPI_SESSION_FINALIZE 
as well."

I'll try to update the proposal before the meeting to have text for both 
possible solutions. 

__________________________
#676 Errata: 'Pending operation' not defined, pending proper definition  
Rolf,Joseph
     Issue https://github.com/mpi-forum/mpi-issues/issues/676
     PR    https://github.com/mpi-forum/mpi-standard/pull/824
     PDF   
https://github.com/mpi-forum/mpi-standard/files/11668075/mpi41-report_Issue676_PR824.pdf

       Substituting "pending operation" by "active operation"

  or PR  https://github.com/mpi-forum/mpi-standard/pull/825
     PDF 
https://github.com/mpi-forum/mpi-standard/files/11669354/mpi41-report_Issue676_PR825.pdf

       Defining "pending operation" as "active operation" (see page 12)

Best regards
Rolf


----- Original Message -----
> From: "Rolf Rabenseifner" <rabenseif...@hlrs.de>
> To: "Main MPI Forum mailing list" <mpi-forum@lists.mpi-forum.org>
> Cc: "Christoph Niethammer" <nietham...@hlrs.de>, "Puri Bangalore" 
> <pvbangal...@ua.edu>, "Joseph Schuchart"
> <schuch...@icl.utk.edu>
> Sent: Wednesday, May 24, 2023 1:36:42 PM
> Subject: Re: Update: Vote announcement for the July 2023 meeting of the MPI 
> Forum

> Martin, Wes, and all,
> 
> I expect that we should reserve also June 14, 2023 for a possible continuation
> of open questions resulting from the discussions of
> 
>> #705/PR822, #710/PR823, and #676/PR824 are now finalized at least for the
>> virtual forum meeting, June 7, 2023
> 
> and other pending items for MPI-4.1 from the June 7 virtual forum meeting.
> 
> Best regards
> Rolf
> 
> 
> 
> 
> ----- Original Message -----
>> From: "Rolf Rabenseifner" <rabenseif...@hlrs.de>
>> To: "Main MPI Forum mailing list" <mpi-forum@lists.mpi-forum.org>
>> Cc: "Christoph Niethammer" <nietham...@hlrs.de>, "Puri Bangalore"
>> <pvbangal...@ua.edu>, "Joseph Schuchart"
>> <schuch...@icl.utk.edu>
>> Sent: Thursday, May 11, 2023 8:05:07 PM
>> Subject: Update: Vote announcement for the July 2023 meeting of the MPI Forum
> 
>> Dear forum members,
>> 
>> #705/PR822, #710/PR823, and #676/PR824 are now finalized at least for the
>> virtual forum meeting, June 7, 2023, details below:
>> 
>>    #705 Errata: Fortran has only compile-time constants    Rolf,Joseph
>>      Issue https://github.com/mpi-forum/mpi-issues/issues/705
>>            (together with https://github.com/mpi-forum/mpi-issues/issues/657 
>>   Rolf, Jeff
>>            H.)
>>      PR    https://github.com/mpi-forum/mpi-standard/pull/822
>>      PDF
>>      
>> https://github.com/mpi-forum/mpi-standard/files/11450065/mpi41-report_Issue705%2B657_PR822.pdf
>> 
>>    #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect   
>>  Rolf
>>      Issue https://github.com/mpi-forum/mpi-issues/issues/710
>>      PR    https://github.com/mpi-forum/mpi-standard/pull/823
>>      PDF
>>      
>> https://github.com/mpi-forum/mpi-standard/files/11454896/mpi41-report_Issue710_PR823.pdf
>> 
>>    #676 Errata: 'Pending operation' not defined, pending proper definition
>>    Rolf,Joseph
>>      Issue https://github.com/mpi-forum/mpi-issues/issues/676
>>      PR    https://github.com/mpi-forum/mpi-standard/pull/824
>>      PDF
>>      
>> https://github.com/mpi-forum/mpi-standard/files/11443976/mpi41-report_Issue676_PR824.pdf
>> 
>> The agenda of the virtual meeting should be reading and discussions if 
>> needed.
>> I did the proposals based on the discussion and the major goals:
>> - backward compatible,
>> - no performance drawbacks on critical paths,
>> - full consistency of the solution with all related parts of the MPI 
>> standard.
>> 
>> If I have overseen something, then my apologies.
>> 
>> If somebody wants to provide a completely different solution to one of these
>> issues,
>> please feel free to do it.
>> - Thanks to Joseph who did PR 822, which was such a counter proposal for 
>> #705.
>> - This method is often better than doing many change requests for the given 
>> PR.
>>   and it helps to completely check whether it is really consistent over
>>   all related parts of the MPI standard.
>> - And thanks for all the comments so far. They really helped me a lot for
>> preparing the three PRs.
>> 
>> I'll be the next three weeks on vacation.
>> 
>> Best regards
>> Rolf Rabenseifner
>> 
>> 
>> ----- Original Message -----
>>> From: "Rolf Rabenseifner" <rabenseif...@hlrs.de>
>>> To: "Main MPI Forum mailing list" <mpi-forum@lists.mpi-forum.org>
>>> Cc: "Christoph Niethammer" <nietham...@hlrs.de>, "Puri Bangalore"
>>> <pvbangal...@ua.edu>, "Joseph Schuchart"
>>> <schuch...@icl.utk.edu>
>>> Sent: Tuesday, May 9, 2023 6:07:04 PM
>>> Subject: Vote announcement for the July 2023 meeting of the MPI Forum
>> 
>>> Dear forum members,
>>>                       (correction: it is for the July 2023 meeting)
>>> 
>>> I would like to make the following announcements for the next MPI Forum 
>>> Meeting
>>> (July 10-13, 2023):
>>> 
>>> - 2nd votes on
>>>    #669 Add operation state 'enabled' and 'local calls' into Terms    Rolf
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/669
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/788
>>> 
>>>    #457 Improvements around the word "rank" in the Process Topologies 
>>> chapter
>>>    Christoph,Rolf
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/457
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/804
>>>      
>>>    #485 Fix Incorrect Usage of Rank/Task/etc. in Language Bindings Chapter
>>>    Rolf,Puri
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/485
>>>      PR     https://github.com/mpi-forum/mpi-standard/pull/803
>>>      PDF
>>>      
>>> https://github.com/mpi-forum/mpi-standard/files/10831598/mpi41-report_Issue485_PR803.pdf
>>> 
>>> - errata reading and vote on
>>> 
>>>    #679 Errata: Noncollective (for procedure) and nonpersistent are not 
>>> defined
>>>    Rolf
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/679
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/820
>>>      PDF
>>>      
>>> https://github.com/mpi-forum/mpi-standard/files/11432286/mpi41-report_Issue679_PR820.pdf
>>> 
>>> - pre-announcement for errata reading and vote on
>>>  --> See also virtual meeting, June 7, 2023 !!!
>>> 
>>>    #705 Errata: Fortran has only compile-time constants    Rolf,Joseph
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/705
>>>            (together with 
>>> https://github.com/mpi-forum/mpi-issues/issues/657   Rolf, Jeff
>>>            H.)
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/822
>>> 
>>>    #710 Errata: 'Pending communication' not defined in MPI_Comm_disconnect  
>>>   Rolf
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/710
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/823
>>> 
>>>    #676 Errata: 'Pending operation' not defined, pending proper definition
>>>    Rolf,Joseph
>>>      Issue https://github.com/mpi-forum/mpi-issues/issues/676
>>>      PR    https://github.com/mpi-forum/mpi-standard/pull/824
>>> 
>>> Best regards
>>> Rolf Rabenseifner
>> 
>> 
>> --
>> Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseif...@hlrs.de .
>> High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 .
>> University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner .
>> Nobelstr. 19, 70569 Stuttgart, Germany
> 
> --
> Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseif...@hlrs.de .
> High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 .
> University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner .
> Nobelstr. 19, 70569 Stuttgart, Germany

-- 
Dr. Rolf Rabenseifner . . . . . . . . . .. . . rabenseif...@hlrs.de .
High Performance Computing Center (HLRS) . . . ++49(0)711/685-65530 .
University of Stuttgart . . . . . . www.hlrs.de/people/rabenseifner .
Nobelstr. 19, 70569 Stuttgart, Germany
_______________________________________________
mpi-forum mailing list
mpi-forum@lists.mpi-forum.org
https://lists.mpi-forum.org/mailman/listinfo/mpi-forum

Reply via email to