Skip to content

Some __kernel_name_generator usages doesn't depends from _ExecutionPolicy type #2083

Closed
@SergeyKopienko

Description

@SergeyKopienko

Describe the Bug:
Some __kernel_name_generator usages doesn't includes _ExecutionPolicy type,
but the code where it's implemented contains _ExecutionPolicy inside template params.
This situation allows to write the code with the different _ExecutionPolicy types but to have the same KernelName inside - it's will generate an error in unnamed lambdas switched off.

To Reproduce:
No reproducers.

Expected Behavior:
Probably every __kernel_name_generator should depends on _ExecutionPolicy type if it is used for code specialization.

Additional Context:
Add any other context about the problem here.

Examples where _ExecutionPolicy type is not used in __kernel_name_generator :

using _LocalScanKernel = oneapi::dpl::__par_backend_hetero::__internal::__kernel_name_generator<

using _GroupScanKernel = oneapi::dpl::__par_backend_hetero::__internal::__kernel_name_generator<

using _ReduceKernel = oneapi::dpl::__par_backend_hetero::__internal::__kernel_name_generator<

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions