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.

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

Fixup cl_khr_command_buffer after extension spec unification #1089

Merged
merged 1 commit into from
Mar 26, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
5 changes: 0 additions & 5 deletions api/cl_khr_command_buffer.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -205,11 +205,6 @@ features:
** {clCommandSVMMemcpyKHR}
** {clCommandSVMMemFillKHR}

=== New Structures

* {cl_command_buffer_khr_TYPE}
* {cl_mutable_command_khr_TYPE}

=== New Types

* {cl_device_command_buffer_capabilities_khr_TYPE}
Expand Down
5 changes: 4 additions & 1 deletion api/opencl_runtime_layer.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -14145,7 +14145,10 @@ returned in _errcode_ret_:
specified by {CL_DEVICE_COMMAND_BUFFER_REQUIRED_QUEUE_PROPERTIES_KHR}.
* {CL_INVALID_CONTEXT} if all the command-queues in _queues_ do not have
the same OpenCL context.
* {CL_INVALID_VALUE} if _num_queues_ is zero.
* {CL_INVALID_VALUE} if the `<<cl_khr_command_buffer_multi_device>>`
extension is supported and _num_queues_ is zero, or if the
`<<cl_khr_command_buffer_multi_device>>` extension is not supported
and _num_queues_ is not one.
EwanC marked this conversation as resolved.
Show resolved Hide resolved
* {CL_INVALID_VALUE} if _queues_ is `NULL`.
* {CL_INVALID_VALUE} if values specified in _properties_ are not valid, or
if the same property name is specified more than once.
Expand Down