Skip to content

Conversation

@hppritcha
Copy link
Member

The user who was reporting these problems was using
the Open MPI 1.10.2 but it almost certainly impacts
other branches.

@rhc54 - let me know if this wording looks good enough.

Signed-off-by: Howard Pritchard howardp@lanl.gov

@hppritcha hppritcha added this to the v2.0.2 milestone Dec 23, 2016
@hppritcha hppritcha requested a review from rhc54 December 23, 2016 17:28
@hppritcha
Copy link
Member Author

I'll update readme on master and then PR to v2.1 and v1.10.x if you think that's needed.

Copy link
Contributor

@rhc54 rhc54 left a comment

Choose a reason for hiding this comment

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

I would suggest adding the following:

These are known issues, and the recommended solution is to avoid those two versions of the compiler suite.

@rhc54
Copy link
Contributor

rhc54 commented Dec 23, 2016

It won't hurt to include it in 1.10 just in case we release another version of it. Thanks!

The user who was reporting these problems was using
the Open MPI 1.10.2 but it almost certainly impacts
other branches.

Signed-off-by: Howard Pritchard <howardp@lanl.gov>
@hppritcha hppritcha force-pushed the topic/update_readme_with_intel_16_bug_note branch from 00ee46d to d45248d Compare December 23, 2016 17:58
@hppritcha
Copy link
Member Author

not waiting for CI as this is just documentation

@hppritcha hppritcha merged commit d52901e into open-mpi:v2.0.x Dec 23, 2016
@hppritcha hppritcha deleted the topic/update_readme_with_intel_16_bug_note branch May 2, 2018 02:56
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.

2 participants