|
20 | 20 | == Notice
|
21 | 21 |
|
22 | 22 | [%hardbreaks]
|
23 |
| -Copyright (C) 2022-2023 Intel Corporation. All rights reserved. |
| 23 | +Copyright (C) 2022-2024 Intel Corporation. All rights reserved. |
24 | 24 |
|
25 | 25 | Khronos(R) is a registered trademark and SYCL(TM) and SPIR(TM) are trademarks
|
26 | 26 | of The Khronos Group Inc. OpenCL(TM) is a trademark of Apple Inc. used by
|
@@ -407,36 +407,7 @@ _Returns_: The number of work-groups or work-items of `Scope` hierarchy level wi
|
407 | 407 |
|
408 | 408 | `root_group` provides an alternative representation of the work-items executing
|
409 | 409 | an ND-range kernel and exposes equivalent functionality to `sycl::nd_item` for
|
410 |
| -querying a work-item's position in the global range. In order to provide access |
411 |
| -to information pertaining to a work-item's position in the work-group or |
412 |
| -sub-group local range, `root_group` needs to provide a new mechanism to access |
413 |
| -instances of the `sycl::group` and `sycl::sub_group` classes. The |
414 |
| -`get_child_group` function provides a general form of this mechanism, allowing |
415 |
| -developers to move down the hierarchy of fixed topology groups. |
416 |
| - |
417 |
| -[source,c++] |
418 |
| ----- |
419 |
| -template <typename Group> |
420 |
| -/* type of child group */ get_child_group(Group g); |
421 |
| ----- |
422 |
| -_Constraints_: `Group` must be one of `root_group` or `sycl::group`. |
423 |
| - |
424 |
| -_Returns_: An instance of another fixed topology group type, representing the |
425 |
| -child of group _g_ to which the calling work-item belongs. If `Group` is |
426 |
| -`root_group`, the child group type is `sycl::group` with the same |
427 |
| -dimensionality. If `Group` is `sycl::group`, the child group type is |
428 |
| -`sycl::sub_group`. |
429 |
| - |
430 |
| -NOTE: Although `sycl::sub_group` is a fixed topology group, it is currently |
431 |
| -the lowest level of the hierarchy and cannot be passed to `get_child_group`. |
432 |
| - |
433 |
| -NOTE: This extension does not provide a `get_parent_group` function because it |
434 |
| -would be easy to use incorrectly. It is good practice for a function accepting |
435 |
| -a group _g_ to only use the work-items in that group, to assist developers in |
436 |
| -reasoning about requirements of the call context (e.g. converged control flow). |
437 |
| -Dividing a group into its children is consistent with this practice, whereas |
438 |
| -accessing the parent group is not. Developers seeking this functionality should |
439 |
| -use the free function queries instead. |
| 410 | +querying a work-item's position in the global range. |
440 | 411 |
|
441 | 412 |
|
442 | 413 | === Synchronizing a `root_group`
|
|
0 commit comments