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

reductions: add note about FP associativity #16

Merged
merged 4 commits into from
Oct 9, 2024

Conversation

davidozog
Copy link
Owner

Summary of changes

Regarding this issue:
https://github.com/orgs/openshmem-org/projects/5/views/1?pane=issue&itemId=74045800

The WG decided to defer something like PR #14, which adds the requirements regarding the reproducibilty of OpenSHMEM reductions on floating-point datatypes.

This PR briefly explains the issue in an API note, and says a future version of the specification may clarify the behavior of reductions on floating-point datatypes.

Proposal Checklist

  • Link to issue(s)
  • Changelog entry
  • Reviewed for changes to front matter
  • Reviewed for changes to back matter

@davidozog davidozog mentioned this pull request Oct 9, 2024
4 tasks
@davidozog
Copy link
Owner Author

If we'd like to indicate this change is an erratum, that PR is now updated here:
kwaters4#8

Copy link

Choose a reason for hiding this comment

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

In the API note, the proposal is going to be silent on statements like the following

  • that the result should be the same on all PEs
  • that the result should be the same if the operation is called multiple times on the same data during the same run
  • that the result should be the same from run to run
  • that the result may be different on different architectures, due to differing arithmetic
  • that the result on IEEE-754 compatible platforms should always be the same everywhere and everywhen
  • that we might consider new APIs or environment variables that enforce more consistent results

Copy link

Choose a reason for hiding this comment

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

This is a nice summary of the open issues. Can you capture it on the follow-up issue for OpenSHMEM 1.7 (and create said issue if we don't have one already)?

Copy link
Owner Author

Choose a reason for hiding this comment

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

content/programming_model_overview.tex Outdated Show resolved Hide resolved
content/shmem_reductions.tex Outdated Show resolved Hide resolved
Copy link

@jdinan jdinan left a comment

Choose a reason for hiding this comment

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

Thanks for preparing this! I made a couple small suggestions, but I think this is the right change to incorporate in 1.6. And you've already made great progress toward clarifications for 1.7.

Copy link

@lstewart lstewart left a comment

Choose a reason for hiding this comment

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

ok fine

Copy link

@jdinan jdinan left a comment

Choose a reason for hiding this comment

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

:shipit:

@davidozog davidozog merged commit c2addc4 into collectives_section-v1.6-RC2 Oct 9, 2024
1 check passed
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.

3 participants