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

Separate the datapar algorithms #5157

Closed
hkaiser opened this issue Feb 9, 2021 · 3 comments · Fixed by #5328
Closed

Separate the datapar algorithms #5157

hkaiser opened this issue Feb 9, 2021 · 3 comments · Fixed by #5328

Comments

@hkaiser
Copy link
Member

hkaiser commented Feb 9, 2021

Currently, our parallel algorithms support being used with the datapar execution policy. This is a remnant of an older standardization proposal. This implementation is currently tightly entangled with the implementation of the parallel base algorithms.

We should do two things:

  • separate the datapar implementations and expose them through separate algorithm specializations (based on the tag_invoke customization point mechanism we have implemented)
  • adapt the implementation to support (and rely on) the data-parallel Types introduced by N4755, section 9, this implies removing datapar as it is today,

This work could also go hand-in-hand with #2271.

@toktarev
Copy link

I've started working on this issue

@hkaiser
Copy link
Member Author

hkaiser commented Apr 13, 2021

@toktarev Please coordinate with @srinivasyadav18 as he is looking into related tasks.

@toktarev
Copy link

Do we really need to "separate the datapar implementations" if we are going to "removing datapar as it is today" ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants