Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remaining Issues #400

Closed
18 of 20 tasks
schulzm opened this issue Dec 10, 2020 · 5 comments
Closed
18 of 20 tasks

Remaining Issues #400

schulzm opened this issue Dec 10, 2020 · 5 comments
Assignees
Labels
Chapter Committee Change Changes to be made by the respective chapter committee(s)
Milestone

Comments

@schulzm
Copy link

schulzm commented Dec 10, 2020

Problem

Keeping Track of other items to be fixed for MPI 4.0 / Found during the Dec Meeting

  • MPI 3.2 in Table 2.1 (is this fixed with PR 402?)
  • Fix spacing, if possible, before the C-Bindings heading (page 830) - STILL OPEN
  • Rolf to check on max length of Fortran identifiers (35?, 38?) - ASKED ROLF
  • Need changelog entry for RMA; in particular for locks being usable in all memory regions
  • Add comma after that on Page 773, line 44-47, chapter 16.4 - FIXED IN PR
  • [n/a] INOUT Split Type, comments made by Wesley and Guillaume - can't find it anymore, let it go for now
  • Remove FROM_GROUP_STRINGTAG (Issue 382??? - adjust example on page 500)
  • All CCs check history text in intro
  • Removing the length limits for C
  • Issue that needs to be added to Issue 280 (remove P2P after rank translate)
  • Fix the IN/INOUT item for info routines (with small fix now and new issue to cover MPI 4.1)
  • Intro text for backwards incompatibility chapter
  • Look at Diff for Collectives Chapter
  • Look at Diff for I/O Chapter
  • Sort changelog entries (at the end)
  • Rolf to talk to Martin Ruefenacht about Python Issues in Appendix A (regarding hyperlinks/references)
  • Datatypes chapter: "input datatype" should be "old datatype" again - FIXED IN PR
  • Decide on how to add space in datatype chapter between COMBINER tables
  • After binding for MPI_Cart_rank, remove "as they are used by the point-to-point routines"

Keeping Track of other items to be fixed for MPI 4.0 / Found after the Dec Meeting

  • PSET_NAME_LEN should have a minimum, too
  • Fix first item in list when MPI_COMM_SPLIT_TYPE returns NULL communicator - first item "No info key is provided." seems wrong - ASKED GUILLAUME
@schulzm schulzm self-assigned this Dec 10, 2020
@wesbland wesbland self-assigned this Dec 10, 2020
@wesbland wesbland added Chapter Committee Change Changes to be made by the respective chapter committee(s) mpi-4.0 labels Dec 10, 2020
@wesbland wesbland added this to Triage in MPI 4.0 Ratification via automation Dec 10, 2020
@wesbland wesbland added this to the 2020-12 milestone Dec 10, 2020
@wesbland wesbland moved this from Triage to To Do for MPI 4.0 in MPI 4.0 Ratification Dec 16, 2020
@wesbland
Copy link
Member

wesbland commented Jan 6, 2021

@schulzm I'm not sure how to track which, if any of these are being / have been addressed. Do you know about the status of any of this? Maybe we should discuss it during the virtual meeting on Friday, but it'll be to late to do anything about it if things aren't done.

@hppritcha
Copy link

FROM_GROUP_STRINGTAG issue was fixed via https://github.com/mpi-forum/mpi-standard/pull/400

@RolfRabenseifner
Copy link

Chapter 1, page 8: Chapter 17, Removed Interfaces, describes routines and constructs that have been
removed from MPI. Some of these were deprecated in MPI-2, and the MPI Forum
decided to remove these from the MPI-3 standard. Others of these were deprecated
in MPI-3, and the MPI Forum decided to remove these from the MPI-4 standard.

The highlighted sentence is completely wrong and should be removed.
Table 2.1 on page 23 and Chapter 17 does not show any deprecated feature inMPI-3.0 or 3.1 and also no removed stuff in MPI-4.0.

@wesbland
Copy link
Member

wesbland commented Jan 12, 2021

Chapter 1, page 8: Chapter 17, Removed Interfaces, describes routines and constructs that have been
removed from MPI. Some of these were deprecated in MPI-2, and the MPI Forum
decided to remove these from the MPI-3 standard. Others of these were deprecated in MPI-3, and the MPI Forum decided to remove these from the MPI-4 standard.

The highlighted sentence is completely wrong and should be removed.
Table 2.1 on page 23 and Chapter 17 does not show any deprecated feature inMPI-3.0 or 3.1 and also no removed stuff in MPI-4.0.

This is a good point. Let's make this a new issue and make sure it gets fixed.

EDIT: There is now a PR to address this attached to the other issue.

@GuillaumeMercier
Copy link

Fix first item in list when MPI_COMM_SPLIT_TYPE returns NULL communicator - first item "No info key is provided."
was addressed by PR 484 ( mpi-forum/mpi-standard/pull/484 ). It now has an issue attached to it (/issues/430) so that @wesbland can keep track of it.

@wesbland wesbland moved this from To Do for MPI 4.0 to In Progress in MPI 4.0 Ratification Jan 13, 2021
MPI 4.0 Ratification automation moved this from In Progress to Done Jan 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chapter Committee Change Changes to be made by the respective chapter committee(s)
Projects
No open projects
Development

No branches or pull requests

5 participants