-
Updated
Jul 8, 2022 - Python
mpi
Here are 1,637 public repositories matching this topic...
The documentation for the function shmem_wait seems inconsistent with the function signatures as it describes parameters target, pe, and value that are actually not part of the interface. The parameter ivar is described but at least in the C interface the variable is named var (without the prefix i).
See https://github.com/open-mpi/ompi/blob/master/oshmem/shmem/man/man3/shmem_wai
-
Updated
Jul 7, 2022 - Fortran
-
Updated
Jul 8, 2022 - C++
-
Updated
Jul 8, 2022 - C
-
Updated
Jul 8, 2022 - C
-
Updated
Jul 6, 2022 - C++
-
Updated
Jul 8, 2022 - Python
-
Updated
Apr 28, 2022 - C
-
Updated
Apr 14, 2022 - C++
-
Updated
Nov 16, 2019 - C++
-
Updated
Jun 23, 2022 - C
-
Updated
Apr 21, 2022 - C++
-
Updated
Jun 29, 2022 - C++
-
Updated
Jun 23, 2022 - Julia
-
Updated
Jul 8, 2022 - C++
-
Updated
Jun 2, 2022 - Jupyter Notebook
-
Updated
May 9, 2022 - Python
-
Updated
May 19, 2022 - Python
-
Updated
Jun 22, 2022 - C++
-
Updated
Apr 6, 2022 - Go
-
Updated
Jul 7, 2022 - C++
-
Updated
Jun 22, 2022 - C++
I recently ran the build with the stylecheck and found out a significant number of warnings.
We need to do the following
- Enable style check for every build
- Fix the current warnings
-
Updated
Jul 5, 2022 - C++
Improve this page
Add a description, image, and links to the mpi topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the mpi topic, visit your repo's landing page and select "manage topics."
Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)