-
Notifications
You must be signed in to change notification settings - Fork 787
[SYCL] Add test for extended deleters #11344
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
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
5a13e4d
Re add extended deleters
3460ade
Revert delete call
310e8d0
Add extended deleters test
c8267b1
Update sycl/test/extended_deleters/extended_deleters.cpp
hdelan c7d258b
Revert "Update sycl/test/extended_deleters/extended_deleters.cpp"
0dc75c2
Remove change to adapter
bbd1e52
Move test to test-e2e
650bb36
Change UR repo and sha
11b9d83
Merge branch 'sycl' into fix-typo-in-hip-adapter
hdelan d0286d9
Only run for HIP, CUDA
0f6ee56
Update commit SHA in UR repo
9aa3a27
Update SHA
b2993ce
Revert "Update SHA"
f2489be
Merge branch 'sycl' into fix-typo-in-hip-adapter
8d05088
Point SHA to reverted commit branch
9788c42
Update sycl/plugins/unified_runtime/CMakeLists.txt
hdelan 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
// REQUIRES: hip, cuda | ||
|
||
// RUN: %{build} -o %t.out | ||
// RUN: %{run} %t.out | FileCheck %s | ||
|
||
// CHECK: This extended deleter should be called at ctx destruction. | ||
|
||
#include <sycl/sycl.hpp> | ||
|
||
int main() { | ||
sycl::context c; | ||
sycl::detail::pi::contextSetExtendedDeleter( | ||
c, | ||
[](void *) { | ||
printf("This extended deleter should be called at ctx destruction."); | ||
}, | ||
nullptr); | ||
} | ||
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.
Why do we need it here and not in the UR repo? This makes no sense to me...
sycl::detail::pi
has to be eradicated from the sycl repo, IMO.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.
If the test does move to UR it'll need to be in a separate PR.
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.
We already have a test for this in the UR repo but this is something that is used in oneMKL through the
sycl::detail::pi
interface. I think it's worthwhile having a test to make sure that the SYCL interface is working as well as the UR one.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.
@aelovikov-intel see here https://github.com/oneapi-src/unified-runtime/blob/main/test/conformance/context/urContextSetExtendedDeleter.cpp
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.
That is bad...
detail
shouldn't be used in production.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 agree but I think that ship has sailed. See here https://github.com/oneapi-src/oneMKL/blob/develop/src/blas/backends/cublas/cublas_scope_handle.cpp#L123
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.
There have been some changes in UR contexts of late, and when these are settled we are going to re-review this entry point and see if we can potentially remove it from oneMKL, but as it stands it is necessary
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've submitted uxlfoundation/oneMath#401. Personally, I'm in favor of removing the test: we do not guarantee availability of the tested functionality. The fact that it resides in
sycl::detail
namespace explicitly communicates that.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 think we should remove this test whenever we stop using this in oneMKL. The reason why I am adding this test is because this functionality was accidentally removed, and since there was no testing for it we didn't realise that something was broken, and oneMKL ended up breaking.