Skip to content

spml/yoda: fix compiler warning #2024

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

Closed
wants to merge 1 commit into from

Conversation

jsquyres
Copy link
Member

This is really only a partial fix. Per #2023, the (oshmem_proc_t) and (ompi_proc_t) types should be unified properly (e.g., oshmem_proc_t should inherit an ompi_proc_t, or something like that). The fact that this code works by casting between two unrelated types is fragile and susceptible to break in the future.

Signed-off-by: Jeff Squyres [email protected]

This is really only a partial fix.  Per
open-mpi#2023, the (oshmem_proc_t) and
(ompi_proc_t) types should be unified properly (e.g., oshmem_proc_t
should inherit an ompi_proc_t, or something like that).  The fact that
this code works by casting between two unrelated types is fragile and
susceptible to break in the future.

Signed-off-by: Jeff Squyres <[email protected]>
@jsquyres
Copy link
Member Author

I think that this PR was made moot by #2026 and open-mpi/ompi-release#1358.

@jsquyres jsquyres closed this Sep 26, 2016
@jsquyres jsquyres deleted the pr/oshmem-warning-fix branch September 26, 2016 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant