Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add multi-device wording to clCommandBarrierWithWaitListKHR #1146

Merged
merged 1 commit into from
Jul 16, 2024
Merged

Add multi-device wording to clCommandBarrierWithWaitListKHR #1146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 19 additions & 5 deletions api/opencl_runtime_layer.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14381,10 +14381,17 @@ include::{generated}/api/protos/clCommandBarrierWithWaitListKHR.txt[]
include::{generated}/api/version-notes/clCommandBarrierWithWaitListKHR.asciidoc[]

* _command_buffer_ refers to a valid command-buffer object.
* _command_queue_ specifies the command-queue the command will be recorded
to.
This parameter is unused, as only a single
command-queue is supported, and **must** be `NULL`.
* _command_queue_ specifies the command-queue the command will be recorded to.
{empty} +
If the {cl_khr_command_buffer_multi_device_EXT} extension is not supported,
only a single command-queue is supported, and _command_queue_ must be
`NULL`.
ifdef::cl_khr_command_buffer_multi_device[]
{empty} +
If the {cl_khr_command_buffer_multi_device_EXT} extension is supported and
_command_queue_ is `NULL`, then only one command-queue must have been set on
_command_buffer_ creation; otherwise, _command_queue_ must not be `NULL`.
endif::cl_khr_command_buffer_multi_device[]
* _sync_point_wait_list_, _num_sync_points_in_wait_list_ specify
synchronization-points that need to complete before this particular
command can be executed.
Expand Down Expand Up @@ -14432,7 +14439,14 @@ recorded after it do not execute until it completes.
executed successfully.
Otherwise, it returns one of the following errors:

* {CL_INVALID_COMMAND_QUEUE} if _command_queue_ is not `NULL`.
* {CL_INVALID_COMMAND_QUEUE} if the
{cl_khr_command_buffer_multi_device_EXT} extension is not supported and
_command_queue_ is not `NULL`.
* {CL_INVALID_COMMAND_QUEUE} if the
{cl_khr_command_buffer_multi_device_EXT} extension is supported; and
either _command_queue_ is `NULL` and _command_buffer_ was created with
more than one queue, or _command_queue_ is not `NULL` and not a
command-queue listed on _command_buffer_ creation.
* {CL_INVALID_COMMAND_BUFFER_KHR} if _command_buffer_ is not a valid
command-buffer.
* {CL_INVALID_CONTEXT} if the context associated with _command_queue_ and
Expand Down