Skip to content

[SYCL] Extend static_assert's message for lambda captures' size #6681

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.

Sign up for GitHub

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
steffenlarsen merged 2 commits into from
Sep 2, 2022
Merged

[SYCL] Extend static_assert's message for lambda captures' size #6681

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
13a9fc5
[SYCL] Extend static_assert's message for lambda captures' size
aelovikov-intel Aug 31, 2022
4d600e9
Update sycl/include/sycl/handler.hpp
aelovikov-intel Aug 31, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions sycl/include/sycl/handler.hpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -730,10 +730,14 @@ class __SYCL_EXPORT handler {
// Some host compilers may have different captures from Clang. Currently
// there is no stable way of handling this when extracting the captures, so
// a static assert is made to fail for incompatible kernel lambdas.
static_assert(!KernelHasName || sizeof(KernelFunc) == KI::getKernelSize(),
"Unexpected kernel lambda size. This can be caused by an "
"external host compiler producing a lambda with an "
"unexpected layout. This is a limitation of the compiler.");
static_assert(
!KernelHasName || sizeof(KernelFunc) == KI::getKernelSize(),
"Unexpected kernel lambda size. This can be caused by an "
"external host compiler producing a lambda with an "
"unexpected layout. This is a limitation of the compiler."
"In many cases the difference is related to capturing constexpr "
"variables. In such cases removing constexpr specifier aligns the "
"captures between the host compiler and the device compiler.");

// Empty name indicates that the compilation happens without integration
// header, so don't perform things that require it.
Expand Down