Skip to content

Conversation

gmlueck
Copy link
Contributor

@gmlueck gmlueck commented Sep 5, 2025

The overloads of parallel_for and nd_launch that take a sycl::kernel object should not allow the application to specify a name for the kernel. The kernel which is invoked by these overloads is determined at runtime (by the value of the sycl::kernel object), so it's not possible to assign a static name.

The implementation was already correct, so this is just fixing a documentation bug.

The overloads of `parallel_for` and `nd_launch` that take a
`sycl::kernel` object should not allow the application to specify a
name for the kernel.  The kernel which is invoked by these overloads
is determined at runtime (by the value of the `sycl::kernel` object),
so it's not possible to assign a static name.

The implementation was already correct, so this is just fixing a
documentation bug.
@gmlueck gmlueck requested a review from a team as a code owner September 5, 2025 19:04
Copy link
Contributor

@jbrodman jbrodman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

github-actions bot commented Sep 8, 2025

@intel/llvm-gatekeepers please consider merging

@gmlueck
Copy link
Contributor Author

gmlueck commented Sep 9, 2025

@intel/llvm-gatekeepers please consider merging

I agree. @intel/llvm-gatekeepers, I think this is ready to merge.

@againull againull merged commit 5c0a51d into intel:sycl Sep 9, 2025
3 checks passed
@gmlueck gmlueck deleted the gmlueck/no-kernel-name branch September 9, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants