Skip to content

[SYCL] Fix enqueue functions taking both kernel and properties #14743

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

Merged

Conversation

steffenlarsen
Copy link
Contributor

The current implementation of the enqueue free functions taking both a launch_config and a kernel do not properly process the properties. This commit addresses this and adds a static assert about the properties passed to these only applying to the launch of the kernel and not how the compiler handles compiling the kernel.

The current implementation of the enqueue free functions taking both a
launch_config and a kernel do not properly process the properties. This
commit addresses this and adds a static assert about the properties
passed to these only applying to the launch of the kernel and not how
the compiler handles compiling the kernel.

Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
Signed-off-by: Larsen, Steffen <steffen.larsen@intel.com>
Co-authored-by: Sergey Semenov <sergey.semenov@intel.com>
@steffenlarsen steffenlarsen merged commit 33325d4 into intel:sycl Jul 26, 2024
15 checks passed
@@ -266,6 +266,8 @@ template <typename PropertyT> struct PropertyMetaInfo {
static constexpr std::nullptr_t value = nullptr;
};

template <typename> struct HasCompileTimeEffect : std::false_type {};
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's a bad decision to extend generic properties interface (even the internal one) with some trait specific to just a few properties/APIs accepting them.

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.

4 participants