-
Notifications
You must be signed in to change notification settings - Fork 2
Remove get_c_op_from_fortran Auxiliary function #105
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
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I don't really like this approach of setting the value of
MPI_SUM
depending on the implementation, the implementations can have their nuances, e.g. they might changes the value ofMPI_SUM
from version to version etc.This approach isn't something that will work for us, we definitely do need to set it to some random value but that shouldn't be used as a criterion to identify the operation to perform.
Uh oh!
There was an error while loading. Please reload this page.
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.
Does it change? Can you check with other versions ?
As I thought that these are predefined constants they are not meant to be changed
even If that's the case Can't we keep updating the values as we switch to newer versions?
If no then we would discard this approach,
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.
So i checked with the mpich 4.1.1 version it were consistent with the constant values like MPI_SUM, MPI_Double, MPI_INT etc
LEt me check with openmpi for the saame
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.
Yes checked with openmpi 5.0.3 too , it's same
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.
This are the logs supporting the same
For OPenMPI
For MPICH
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.
My concern isn't limited just the (possibly) changing values of constants with different versioning. The dependency of value on the implementation isn't fundamentally the right thing to do, considering that we can have a better solution instead of using this.
I've made a PR here: #107, which intends to do the work that this PR is doing with a different approach (same as what we've already done with other constants like
MPI_COMM_WORLD
etc.I'll let @certik take a call here.
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.
The approach in #107 is fine.
This PR I would need to understand the details, I am not quite sure what is going on, so don't have an 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.
Let's go with #107 approach then
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.
Perfect, I apologize that the effort here seems wasted, but it isn't, once we get with understanding more of the MPI work we might able to better reflect on this approach later.
For now, I'll merged #107
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.
Yes, I always learn from this,,,, How Different Approaches have their own merits and demerits,,
Thanks for bringing that approach!!