-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Align with SYCL 2020: remove sycl::mode_tag_t #1880
Conversation
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
Looks reasonable to me, but why not combine two distinct helpers ("converter" and "resolver") into a single one having two template parameters?
If we are sure it is not only unused but also unnecessary, the first step would be to just set the parameter always to However I am not sure about the tag being unnecessary. Support for C++20 concepts such as |
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
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, happy to reapprove for decay changes if you want to make them.
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
Signed-off-by: Dmitriy Sobolev <dmitriy.sobolev@intel.com>
Thank you. I would prefer leaving it as is with |
sycl::mode_tag_t
is not a part of SYCL 2020. It was a part of the provisional specification, but it is absent in the newer revisions.There is a more radical approach: remove seemingly unused
access_mode
fromsycl_iterator
class entirely, but I am not sure about design / ABI implications.Note, that the host_task tags (such as
read_write_host_task
) were not added, because they are not currently supported, and there is no sense to do so. The oneDPL specification suggest that thebegin
andend
functions should be provided during code submission to a device, which is not applicable within a host task context: