-
Notifications
You must be signed in to change notification settings - Fork 932
sync subarray and darray behaviour #1003
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
Conversation
Basic usage works again for both subarray and darray by using create_hindexed instead of create_resized Test case cited in http://lists.mpich.org/pipermail/discuss/2015-January/003608.html still works
|
@bosilca can you comment? Thanks. |
|
is this related to #965 ? |
|
I haven't seen this issue before posting the pull request, thanks. |
|
Thanks Guillaume, bottom line, is MPI_Type_create_resized broken or not ? in my test case, both mpich and ompi have the same behavior (well, ompi also issues a warning), and this is not the behavior I expected (could be a bug, or my incorrect expectation) |
|
Add @bosilca |
|
We might want to make this issue a blocker on 2.0.0. I remember fixing an issue with subarray but didn't realize darray was also broken. |
|
IMHO #965 is the blocker and the milestone should be v1.10.1 |
|
Due to the emergency of the next release, after talking with Jeff we propose to get the patch proposed here in the 1.10, and create an issue for the trunk. This will give me a little bit more time to dig into the internals of the type_resize and understand what is not going as expected there. |
|
The corresponding issue for the devel version is #1063. |
Fix a potential race condition in which a progress matching thread co…
Basic usage works again for both subarray and darray by using create_hindexed instead of create_resized
Test case cited in http://lists.mpich.org/pipermail/discuss/2015-January/003608.html still works