Problem

Cub allows itself to place into a namespace via CUB_NS_PREFIX and CUB_NS_POSTFIX, such that multiple shared libraries can each utilize their own copy of it (and thus different versions can safely coexist). Static variables used for caching could otherwise cause problems (e.g., https://github.com/NVIDIA/cub/blob/main/cub/util_device.cuh#L212).

Thrust however depends on cub and

DeviceSegmentedReduce reduces each segment using the same kernel as DeviceReduce, and thus provides the same run-to-run consistency guarantee for non-associative types. The documentation for DeviceSegmentedReduce should be updated to reflect this.

E.g. this bit: https://github.com/NVIDIA/cub/blob/a8910accebe74ce043a13026f8e71d678cddd6c1/cub/device/device_reduce.cuh#L91-L95
needs to be ad

I've recently come to realize that the 'one-size-fits-all' mega-snippets on marzer.github.io/tomlplusplus aren't necessarily useful for everyone, and I should break them up into smaller sub-examples. I'd be totally happy to accept help with this, though that may be wishful thinking!

A custom generator for systems documentation. It should parse the system definition and generate a custom page according to our requirements.

The output should list:

• dimension definition and a coherent unit
• quantity alias with a default representation type
• all the units with their UDLs and constants

The problem is that the OpenCL types in https://github.com/triSYCL/triSYCL/blob/master/include/triSYCL/opencl_types.hpp are defined on the host according to the x86-64 Linux ABI which depends on the CPU & OS instead of using the description from https://www.khronos.org/registry/OpenCL/specs/2.2/html/OpenCL_C.html#built-in-scalar-data-types

Note that the system-wide cl_size_t has been removed