-
Notifications
You must be signed in to change notification settings - Fork 738
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
[SYCL] Use inheritance to implement oneapi properties #16024
[SYCL] Use inheritance to implement oneapi properties #16024
Conversation
744852d
to
35c51ea
Compare
35c51ea
to
0e556ce
Compare
0e556ce
to
8fa4d79
Compare
Ping @steffenlarsen |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I especially like how much more readable the constexpr functions are.
sycl::ext::oneapi::experimental::empty_properties_t InvalidPropertyList7{ | ||
sycl::ext::oneapi::experimental::foo{0}}; | ||
/* | ||
// TODO: Uncomment these lines once https://github.com/intel/llvm/issues/13677 | ||
// has been fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suppose #13677 can be closed, even if it's not necessarily fixed? 🤔
# Conflicts: # sycl/test/check_device_code/group_load.cpp # sycl/test/check_device_code/group_store.cpp
This is based on @rolandschulz 's #13776.
The only remaining boost/mp11 usage is to sort/filter properties, I'm going to remove that in a separate PRs.
I've also left multiple utilities (that accept variadic pack) still using
std::tuple
as their implementation detail. That can be cleaned up separately as well.Closes #13677.