-
Notifications
You must be signed in to change notification settings - Fork 10
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
resolve bug with KokkosComm::irecv, add to unit testing #90
Conversation
|
@@ -54,7 +54,7 @@ void test_1d(const View1D &a) { | |||
} else if (1 == rank) { | |||
int src = 0; | |||
MPI_Request req; | |||
KokkosComm::Impl::irecv(a, src, 0, MPI_COMM_WORLD, req); | |||
KokkosComm::irecv(a, src, 0, MPI_COMM_WORLD, req); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is still a difference between isend and irecv: isend returns a request, irecv has an output parameter. Is that on purpose?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwpearson I just saw this, what is your opinion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably have Irecv produce an output as well. I will accept this for now and open an issue against myself to implement it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, irecv was implemented in the KokkosComm namespace erroneously. This bug was not captured via unit testing because unit testing directly called Impl::irecv.