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

platform: Clarify behavior for ATOMIC_SCOPE_ALL_DEVICES #1129 #1171

Merged
Merged
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: 4 additions & 1 deletion api/opencl_platform_layer.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -473,7 +473,7 @@ device except for the following queries:

[[device-queries-table]]
.List of supported param_names by {clGetDeviceInfo}
[width="100%",cols="<33%,<17%,<50%",options="header"]
[width="100%",cols="<28%,<15%,<57%",options="header"]
|====
| Device Info | Return Type | Description
| {CL_DEVICE_TYPE_anchor}
Expand Down Expand Up @@ -1606,6 +1606,9 @@ include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_MEMORY_CAPABILITIES.asci
{CL_DEVICE_ATOMIC_ORDER_RELAXED} \| +
{CL_DEVICE_ATOMIC_SCOPE_WORK_GROUP}

A device that does not support {CL_DEVICE_SVM_ATOMICS} (and hence does not support {CL_MEM_SVM_ATOMICS}) may still support {CL_DEVICE_ATOMIC_SCOPE_ALL_DEVICES}. On these devices, an atomic operation with
*memory_scope_all_svm_devices* will behave the same as if the scope were *memory_scope_device* - refer to the <<memory-consistency-model, memory consistency model>>.

| {CL_DEVICE_ATOMIC_FENCE_CAPABILITIES_anchor}

include::{generated}/api/version-notes/CL_DEVICE_ATOMIC_FENCE_CAPABILITIES.asciidoc[]
Expand Down