-
Notifications
You must be signed in to change notification settings - Fork 802
[SYCL] Implementation of discard_events #5026
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
Changes from 27 commits
adf4079
6905227
aaa71c8
04d798f
1b340b0
aa620d4
f5730c6
2b1a221
2f31823
b08c309
ebaa2a1
d325859
7f5de5b
107721c
16cf4c0
3fd916e
675a1a3
b0b1e0d
23271fd
1a67f7d
c996706
bf96adc
fa654d3
a85eec5
6e4468b
65ef8fe
4cd8233
9ec63ad
d55f3e5
f70f49d
fe6abbf
6617fc7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -287,7 +287,10 @@ enum class event : cl_event_info { | |||||||||
| enum class event_command_status : cl_int { | ||||||||||
| submitted = CL_SUBMITTED, | ||||||||||
| running = CL_RUNNING, | ||||||||||
| complete = CL_COMPLETE | ||||||||||
| complete = CL_COMPLETE, | ||||||||||
| ext_oneapi_unknown = | ||||||||||
| submitted + running + complete + | ||||||||||
| 1 // TODO: a more elegant way to ensure that the unique value is here | ||||||||||
|
||||||||||
| ext_oneapi_unknown = | |
| submitted + running + complete + | |
| 1 // TODO: a more elegant way to ensure that the unique value is here | |
| ext_oneapi_unknown = 1000; |
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.
It would leave enough space for 1:1 mapping if BE supports more statuses.
Maybe @gmlueck have an opinion as well.
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.
You are worried that the value of ext_oneapi_unknown might collide with some future OpenCL extension that adds a new "command execution status" value? It's hard to predict what new values might be added in the future. However, since all values are positive now, it's probably safe to use a negative value. Therefore, you could use -1. If we add other ext_oneapi values in the future, they could be -2, etc.
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.
Ok, I changed it to -1, thanks for the suggestion!
Uh oh!
There was an error while loading. Please reload this page.