Skip to content

opal static mutex initializers #1026

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

Merged
merged 2 commits into from
Oct 15, 2015
Merged

Conversation

hjelmn
Copy link
Member

@hjelmn hjelmn commented Oct 14, 2015

No description provided.

@hjelmn
Copy link
Member Author

hjelmn commented Oct 14, 2015

@bosilca, @jsquyres please take a look.

Some time ago I asked for this support for MPI_T but we chose not to add it because we supported non-posix mutexes. That is no longer the case so we might as well add them.

It might also be worth considering adding an equivalent to pthread_once.

@hjelmn
Copy link
Member Author

hjelmn commented Oct 14, 2015

I may remove the debug initializers since they only set some members to 0. This is already guaranteed by the C standard if the variable being initialized has global or file scope.

Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
Signed-off-by: Nathan Hjelm <hjelmn@lanl.gov>
@jsquyres
Copy link
Member

👍

@hjelmn
Copy link
Member Author

hjelmn commented Oct 14, 2015

One change. Some platforms define PTHREAD_RECURSIVE_MUTEX_INITIALIZER and others use PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP. Added support for the later.

jsquyres added a commit that referenced this pull request Oct 15, 2015
opal static mutex initializers
@jsquyres jsquyres merged commit aceb1eb into open-mpi:master Oct 15, 2015
jsquyres added a commit to jsquyres/ompi that referenced this pull request Aug 23, 2016
…n_missing_mpi_win_constants

fortran: add missing constants for MPI_WIN_CREATE_FLAVOR and MPI_WIN_…
@hjelmn hjelmn deleted the static_mutex branch July 12, 2018 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants