Skip to content

Conversation

@antonwolfy
Copy link
Contributor

@antonwolfy antonwolfy commented Jul 16, 2024

The PR reverts most of the changes done in #1897, because the adaptation to async dpctl execution is completed by the last implemented PRs (#1919, #1922) and so there is no need to have explicit data synchronization point at the end of dpnp functions.

  • Have you provided a meaningful PR description?
  • Have you added a test, reproducer or referred to issue with a reproducer?
  • Have you tested your changes locally for CPU and GPU devices?
  • Have you made sure that new changes do not introduce compiler warnings?
  • Have you checked performance impact of proposed changes?
  • If this PR is a work in progress, are you filing the PR as a draft?

@antonwolfy antonwolfy self-assigned this Jul 16, 2024
@github-actions
Copy link
Contributor

github-actions bot commented Jul 16, 2024

View rendered docs @ https://intelpython.github.io/dpnp/index.html

@antonwolfy antonwolfy marked this pull request as ready for review July 16, 2024 17:00
Copy link
Contributor

@vtavana vtavana left a comment

Choose a reason for hiding this comment

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

Thank you, @antonwolfy!

@antonwolfy antonwolfy merged commit 56a03e8 into master Jul 17, 2024
@antonwolfy antonwolfy deleted the adopt-to-async-dpctl-execution branch July 17, 2024 12:27
github-actions bot added a commit that referenced this pull request Jul 17, 2024
* Remove data sync from arraycreation and histogram functions

* Remove data sync from elementwise functions

* Remove data sync from manipulation functions 56a03e8
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.

2 participants