-
Notifications
You must be signed in to change notification settings - Fork 739
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] wait_and_throw
invokes asynchronous handlers linked to the events that the event depends on.
#12202
base: sycl
Are you sure you want to change the base?
Conversation
wait_and_throw
to invoke asynchronous handlers linked to the events that the occurrence of an event relies on.
wait_and_throw
to invoke asynchronous handlers linked to the events that the occurrence of an event relies on.wait_and_throw
to invoke asynchronous handlers linked to the events that an event depends on.
wait_and_throw
to invoke asynchronous handlers linked to the events that an event depends on.wait_and_throw
invokes asynchronous handlers linked to the events that an event depends on.
d0ad857
to
764f4e9
Compare
…this event relies on.
764f4e9
to
bf9a906
Compare
wait_and_throw
invokes asynchronous handlers linked to the events that an event depends on.wait_and_throw
invokes asynchronous handlers linked to the events that the event depends on.
…requirements between two queues.
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.
LGTM!
@dm-vodopyanov a friendly request for review please. |
@dm-vodopyanov, @Naghasan a friendly request for review please. |
@mmoadeli, the PR doesn't require any extra approvals, since @steffenlarsen is a member of runtime-reviewers team. However, I'm a bit hesitant to merge it right now considering that the spec PR is still open (even though it is approved). Tagging @gmlueck as one of the reviewers for extra inputs. Besides that, I wonder if this should be considered as a breaking change and put under |
thanks @AlexeySachkov |
Since Greg is OOO, I am tagging @Pennycook and @AerialMantis on this. It seems to me like the spec clarification has 2 approvals, so I figure it will get in soon. As to whether this is a breaking change is a good question though. |
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.
Looks good to me, just a suggestion for a further test to catch a further case highlighted in the recent spec discussions.
|
||
int main() { | ||
{ | ||
test_exception_handler teh1; |
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 it could be worth also having a test for the case that @gmlueck highlighted in the spec PR where there is no dependency chain between the two kernels but they are enqueued to the same queue.
It was decided that in this case we should all errors caught by the queue
, so if there is a call to wait
on the queue
then both exceptions should be thrown.
…between the two kernels but they are enqueued to the same queue.
This pull request is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be automatically closed in 30 days. |
@AerialMantis It seems the corresponding spec PR is merged. Could this be merged in? |
Modifies
wait_and_throw
to invoke asynchronous handlers linked to the events that an event depends on.There is a corresponding PR to clarify specification.