Skip to content

Issues: mpi-forum/mpi-issues

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.

Sign up for GitHub

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

313 Open 676 Closed
313 Open 676 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

apis.json for versions of MPI standard should be public
#993 opened Apr 8, 2025 by hppritcha
2
Other minor updates mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#992 opened Apr 1, 2025 by wgropp
Document Conventions mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#990 opened Mar 31, 2025 by wgropp
Minor text improvements mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#989 opened Mar 31, 2025 by wgropp
Fixes for code check editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#988 opened Mar 29, 2025 by wgropp
Overly restrictive statement about thread levels mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#987 opened Mar 29, 2025 by wgropp
Wait/test any/some/all leaves out single request case editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#985 opened Mar 29, 2025 by wgropp
Fix misspelled const in example editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#984 opened Mar 29, 2025 by wgropp
Bad index macro use fix editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#983 opened Mar 29, 2025 by wgropp
Fix grammar issues in RC editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#982 opened Mar 29, 2025 by wgropp
Formatting fixes editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard
#981 opened Mar 29, 2025 by wgropp
Internal mutation of communicator or other MPI objects in relation to C++ const semantics
#980 opened Mar 27, 2025 by correaa
12
ABI: Missing keys "mpi_{integer|logical}16_supported" chap-abi ABI Chapter Committee Chapter Committee Change Changes to be made by the respective chapter committee(s) mpi-5.0 For inclusion in the MPI 5.0 standard wg-abi ABI Working Group
#979 opened Mar 24, 2025 by dalcinl
@jeffhammond
need to fix MPI_Type_size return value for unsupported datatypes in the ABI chap-abi ABI Chapter Committee mpi-5.0 For inclusion in the MPI 5.0 standard
#977 opened Mar 18, 2025 by jeffhammond June 2025
@jeffhammond
28
Remove persistent communication from MPI alltogether
#976 opened Mar 7, 2025 by softwaretraff
Tools Chapter Committee needs update editor change Changes to be made by the document editor mpi-5.0 For inclusion in the MPI 5.0 standard scheduled no-no vote No-No vote is scheduled for the next meeting scheduled reading Reading is scheduled for the next meeting
#975 opened Mar 7, 2025 by mahermanns June 2025
@mahermanns
2
kill MPI_Fint from ABI chap-abi ABI Chapter Committee had reading Completed the formal proposal reading mpi-5.0 For inclusion in the MPI 5.0 standard scheduled first-and-only vote First-and-only vote is scheduled for the next meeting
#972 opened Mar 6, 2025 by jeffhammond June 2025
@jeffhammond
1
Do All-to-All collectives *must* synchronize? chap-collective Collective Communication Chapter Committee chap-terms MPI Terms and Conventions Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#971 opened Mar 5, 2025 by mknobi
4
Description of shared file-pointer movement convoluted chap-io I/O Chapter Committee Chapter Committee Change Changes to be made by the respective chapter committee(s)
#970 opened Mar 5, 2025 by mahermanns
p. 714, l 20, 40ff: It the only normative text outside of an example environment in this section. This is kind of weird without introductory text to the example chap-io I/O Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard wg-io I/O Working Group
#969 opened Mar 5, 2025 by wesbland
\mpilaunch noch hyperref-enabled chap-dynamic Process Initialization, Creation, and Management Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#968 opened Mar 5, 2025 by mahermanns
@mahermanns
pg 528, ln 32 - only mpi_memory_alloc_kinds includes a parenthetical with the value type and default, which looks out of place. perhaps it can be removed, or other keys such as mpi_initial_errhandler can be extended with type and default?" chap-dynamic Process Initialization, Creation, and Management Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#967 opened Mar 5, 2025 by wesbland
"pg 503, ln 20 - comment in example about freeing the group because the library doesn't need it seems out of place. also lib_comm is not used, or at least commented how it might be used. chap-dynamic Process Initialization, Creation, and Management Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard
#966 opened Mar 5, 2025 by wesbland
Page 68 line 34: is a single bullet-point algorithm for send really a "model implementation"? Do we provide a code example/reference implementation elsewhere? chap-p2p Point to Point Communication Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard wg-p2p Point-to-Point Working Group
#965 opened Mar 5, 2025 by wrwilliams
AtoU page 60-61 border: this reads as a deprecation without a deprecation chap-p2p Point to Point Communication Chapter Committee mpi-6 For inclusion in the MPI 5.1 or 6.0 standard wg-p2p Point-to-Point Working Group
#964 opened Mar 5, 2025 by wrwilliams
ProTip! Exclude everything labeled bug with -label:bug.