-
Notifications
You must be signed in to change notification settings - Fork 788
[SYCL] Adapt to sycl 2020 exceptions #9771
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
[SYCL] Adapt to sycl 2020 exceptions #9771
Conversation
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.
Thanks a lot for making these changes! I just have a small request and then it needs to be formatted with clang-format
, then I'm happy with it. 😄
@steffenlarsen Thanks for comments. |
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.
Great, thank you! There seems to be some failing tests due to them expecting the old exceptions, but otherwise it LGTM!
@steffenlarsen thanks |
We need the tests to pass before merging the PR, otherwise it will make other PRs and the post-commit testing fail these tests too. Note that the unittests that fail seem to all be in sycl/unittests/allowlist/ParseAllowList.cpp, trying to catch |
b820f76
to
2a42cf8
Compare
a3a869e
to
95ed228
Compare
95ed228
to
88d14f0
Compare
29f1762
to
a410e75
Compare
@steffenlarsen Thanks for comment |
Thank you, @pwisniewskimobica ! At first glance I don't think any of these failures are related to this patch. Normally it may help to push a merge with tip onto the this patch and let CI run again, though we have been seeing some odd failures in CI today so I cannot promise that it will fix it fully. |
@steffenlarsen thanks |
With the amount of failures in the current version I would prefer if you push a merge commit and hopefully it will at least reduce the number of failures we see. My worry is that if we consider the current failures as unrelated we may miss some that are in fact related. |
@steffenlarsen thanks for help! |
So it did! Thanks again for making these changes. |
Due to issue #7268 I changed old exceptions to new ones (`sycl::exception`)
Due to issue #7268
I changed old exceptions to new ones (
sycl::exception
)