Skip to content
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

#172 Fix calling functions with value arguments in co_reduce #331

Closed
wants to merge 2 commits into from

Conversation

vehre
Copy link
Collaborator

@vehre vehre commented Feb 8, 2017

Fixing co_reduce with value argumented functions and char arrays as arguments.
Fixing co_broadcast cleanup.
Added some testcases.

Fixes #172

Andre Vehreschild and others added 2 commits February 8, 2017 09:25
Add support for recude-functions with value parameters.
Add support for char-arrays as arguments to reduce-functions.
Rename co_reduce_1 to internal_co_reduce to get a better naming.
Create mpi-datatype to transport the char-array length.

Fixes #172.
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ vehre
❌ Andre Vehreschild


Andre Vehreschild seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

@vehre
Copy link
Collaborator Author

vehre commented Feb 8, 2017

Ignore!

@vehre vehre closed this Feb 8, 2017
Copy link
Collaborator

@zbeekman zbeekman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vehre Thanks so much for this PR. This is a CRITICAL bug fix, IMO, and it's great to be finally resolving it.

Can you please associate the email address used for that commit with your github account to satisfy the CLA compliance bot?

Also, if you can address some of my comments I'd appreciate it. If not, I'll rebase/cleanup myself once you're ready.

# remove this before merging into master
set_property(TEST co_reduce-factorial PROPERTY WILL_FAIL TRUE)
# set_property(TEST co_reduce-factorial PROPERTY WILL_FAIL TRUE)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just delete this line entirely please.

co_reduce_1 (MPI_Op op, gfc_descriptor_t *source, int result_image, int *stat,
char *errmsg, int src_len __attribute__ ((unused)), int errmsg_len)
internal_co_reduce (MPI_Op op, gfc_descriptor_t *source, int result_image, int *stat,
char *errmsg, int src_len, int errmsg_len)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to set your editor to use spaces and not tab characters? Also, it would be great to revert the leading indentation whitespace changes, or at least fixup white space in a separate commit from when substantive edits are made.

@@ -3285,17 +3327,17 @@ co_reduce_1 (MPI_Op op, gfc_descriptor_t *source, int result_image, int *stat,
if (rank == 0 || PREFIX (is_contiguous) (source))
{
if (result_image == 0)
ierr = MPI_Allreduce (MPI_IN_PLACE, source->base_addr, size, datatype,
ierr = MPI_Allreduce (MPI_IN_PLACE, source->base_addr, size, datatype,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please revert whitespace only changes by amending the commit if you know how... if not, I'll do it.

result_image-1, CAF_COMM_WORLD);
else
ierr = MPI_Reduce (source->base_addr, NULL, size, datatype, op,
ierr = MPI_Reduce (source->base_addr, NULL, size, datatype, op,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for these two diffs, whitespace only changes...

@zbeekman
Copy link
Collaborator

zbeekman commented Feb 8, 2017

Ignore!

lol OK

btw if you add the WIP (work in progress) label, then you can leave the pull request open and keep working on it and pushing commits, without any danger of someone merging it. Also add that to the title to be safe... then you can just leave it open...

@vehre vehre deleted the vehre/co_reduce_calltype_fix_172 branch February 8, 2017 20:13
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.

None yet

3 participants